Repository navigation
refactor: consume shared ores_flutter primitives - #11
Merged
Merged
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
2 participants
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.
Start Declarative Migrations on the cross-org Flutter shared baseline.
Changes:
ORESoftware/ores-flutterto immutable commitb39f9a1371ddd19289ad46fd5501d20524e5fc56>=3.5.0)OresSpacing.lgThis keeps product/domain code local while moving generic Flutter primitives to the shared core. Shared Auth, Opto Sync, ORES telemetry, flags, and Zed remain capability-specific integrations owned by their respective repositories.