feat: expose consistent factories across Remix stylers#74
Merged
Conversation
…factories # Conflicts: # packages/remix/lib/src/components/textfield/textfield.g.dart # packages/remix/lib/src/components/textfield/textfield_style.dart
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.
Description
This PR migrates all public Remix stylers to generated spec stylers and forwards canonical nested factory surfaces from Mix PR #985, enabling contextual shorthand such as
.onHovered(.color(...))and.onPressed(.scale(...)).It preserves fluent Box conveniences through
RemixBoxStylerMixin, source-authors unchanged Fortal widget shells because same-library shared-part ordering preventsMixWidgetfrom resolving generated stylers on a clean build, and documents the alias, conflict, and migration policy.Representative tests verify factory/fluent equivalence, nested and restricted surfaces, selected-state shorthand, and compatibility with legacy styling behavior.
Validation passed with
fvm dart analyze,fvm dart run melos run dcm:check --scope=remix,fvm dart run melos run test:flutter --no-select, andfvm dart run melos run atlas:fortal:check.Legacy convenience constructors and three conflicting fluent names use documented canonical replacements, so consumers using those APIs must update.
Related Issues
Closes #70.
Checklist
Note: Updating the
pubspec.yamlandCHANGELOG.mdis not required. These are handled automatically during the release process.///).Breaking Change
Does this PR require users of the package to manually update their code?