-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: inline label props have unexpected behavior with new validation #7015
Merged
Conversation
This file contains 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
mihai-albu-sage
force-pushed
the
FE-6666
branch
from
October 11, 2024 09:00
2eb6235
to
42bdda4
Compare
labelInline and legendInline should have no effect with new validation
mihai-albu-sage
force-pushed
the
FE-6666
branch
from
October 11, 2024 09:19
42bdda4
to
922694f
Compare
edleeks87
approved these changes
Oct 23, 2024
Parsium
approved these changes
Oct 23, 2024
paulrobinson88
approved these changes
Oct 25, 2024
🎉 This PR is included in version 144.2.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
labelInline and legendInline should have no effect with new validation
Proposed behaviour
labelInline
orlegendInline
props should have no effect when new validation flag has been set across the following components:DateRange
,NumeralDate
,RadioButtonGroup
,Textarea
DateRange
with new validation flag andlabelInline
- proposed behavior:NumeralDate
with new validation flag andlabelInline
- proposed behavior:RadioButtonGroup
with new validation flag andlegendInline
- proposed behavior:Textarea
with ``new validation flag andlabelInline
- proposed behavior: (no padding-top present that shifts the entire content down).Current behaviour
In certain components,
labelInline
orlegendInline
props change the component alignment when the new validation flag has been set.DateRange
with new validation flag andlabelInline
- current behavior:NumeralDate
with new validation flag andlabelInline
- current behavior:RadioButtonGroup
with new validation flag andlegendInline
- current behavior:Textarea
with ``new validation flag andlabelInline
- current behavior: (padding-top is present and shifts the entire content down)Checklist
d.ts
file added or updated if requiredQA
Additional context
Testing instructions