fix!: set full block field status explicitly#9840
Open
maribethb wants to merge 1 commit intoRaspberryPiFoundation:v13from
Open
fix!: set full block field status explicitly#9840maribethb wants to merge 1 commit intoRaspberryPiFoundation:v13from
maribethb wants to merge 1 commit intoRaspberryPiFoundation:v13from
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The basics
The details
Resolves
Fixes #9838
Proposed Changes
isFullBlockFieldmethod to return false, then overrides it for specific fields that are rendered that wayinternalfrom the above method since custom fields may need to override itsetSizemethod to account for whether or not the borderRect actually existsReason for Changes
Any field that doesn't have a borderRect was falsely claiming to be a full-block field. This includes image and text fields, even if they weren't the only fields on a block. This caused problems when we focus and label full-block fields differently.
Test Coverage
Tests pass and manually verified correct behavior as well, for both zelos and thrasos
Documentation
BREAKING CHANGES
This breaking change only affects you in a few scenarios:
isFullBlockFieldand set it to return true only if the field should be rendered as a full-block field (this includes checking whether the source block is a simple reporter block aka has only one field and has an output connection)FieldInputthat overridesinitViewwithout calling super, or creates a borderRect element that is sometimes hiddenIf none of these apply, then this change should not affect you.