chore: update forms Input forms input 2.6.0 tokens - #911
Open
AhmedAmineZr wants to merge 9 commits into
Open
Conversation
AhmedAmineZr
added
📖 documentation
|
📖 Documentation preview deployed! 🔗 https://flutter.unified-design-system.orange.com/prPreview/911/ |
- Add MIGRATION.md entry for OudsTextInputPrefixIcon/OudsTextInputSuffixIconButton breaking change (prefixIcon/suffixIcon type change, onSuffixPressed removal) - Document OudsButton.tinted as a non-breaking addition - Sync skills/ouds-flutter-migration-guide/SKILL.md with the same migration steps Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- Add v2.0.0 -> v2.1.0 section (Navigation Button, Circular/Linear Progress Indicator, tokens v2.6.0), matching the released CHANGELOG entries - Add v2.1.0 -> v3.0.0 section and move the OudsTextInput/OudsPhoneNumberInput typed prefix/suffix icon breaking change and OudsButton.tinted addition there, since they belong to the upcoming 3.0.0 release (per ouds_core pubspec.yaml and CHANGELOG Unreleased section), not v2.0.0 - Remove those entries from the v1.3.1 -> v2.0.0 section where they had been incorrectly attributed - Sync skills/ouds-flutter-migration-guide/SKILL.md version summary table and the typed icon migration example with the new v2.1.0 -> v3.0.0 section Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
AhmedAmineZr
marked this pull request as ready for review
August 26, 2026 17:45
This was
linked to
issues
Aug 26, 2026
Metadata-only update (phone/short-number metadata, carrier and geocoding data refresh) within the existing ^1.1.51 constraint declared in ouds_core/pubspec.yaml. No API changes; PhoneNumberUtil usage in OudsPhoneNumberInput is unaffected. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
AhmedAmineZr
changed the title
forms Input forms input 2.6.0 tokens
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
1 participant
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.
Note: Please transform
- [ ]into- (NA)in the description when things are not applicableRelated issues
text inputcomponent, update to v1.4.1 #784password input, update to v1.3.1 #785tintedparameter #912Description
phone number inputcomponent, update to v1.3.1 #839Motivation & Context
Types of change
Previews
Checklist
Contribution
Accessibility
Design
Development
Documentation
Checklist (for Core Team only)