fix(force-value-field) - avoid rendering statements without a description#964
Merged
gabrielseco merged 4 commits intomainfrom Apr 28, 2026
Merged
fix(force-value-field) - avoid rendering statements without a description#964gabrielseco merged 4 commits intomainfrom
gabrielseco merged 4 commits intomainfrom
Conversation
Contributor
📦 Bundle Size Report
Size Limits
Largest Files (Top 5)
View All Files (313 total)
✅ Bundle size check passed |
Contributor
📊 Coverage Report✅ Coverage increased! 🎉
Detailed BreakdownLines Coverage
Statements Coverage
Functions Coverage
Branches Coverage
✅ Coverage check passed |
Contributor
|
Deploy preview for remote-flows ready!
Deployed with vercel-action |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 236682b. Configure here.
cammellos
approved these changes
Apr 28, 2026
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.

I was testing GER contract details v3 and I notice a force value field rendering...
I observe in our platform we have a hidden logic to avoid this.
Note
Low Risk
Low risk UI behavior change limited to
ForcedValueFieldrendering conditions, covered by new tests; main impact is that some fields will no longer display when content is empty.Overview
ForcedValueFieldnow renders nothing when there’s no sanitized description and nostatement.title, preventing empty/placeholder forced-value statements from showing up while still callingsetValueon mount.Tests were expanded to assert the hidden-render behavior (
container.firstChildisnull) and to ensure the form value is still set even when the component doesn’t render.Reviewed by Cursor Bugbot for commit aa9872d. Bugbot is set up for automated code reviews on this repo. Configure here.