fix: allow 2-letter topics in pubspec.yaml#5288
Merged
hyperupcall merged 1 commit intoSchemaStore:masterfrom Jan 20, 2026
Merged
fix: allow 2-letter topics in pubspec.yaml#5288hyperupcall merged 1 commit intoSchemaStore:masterfrom
hyperupcall merged 1 commit intoSchemaStore:masterfrom
Conversation
Contributor
|
Thanks for the PR! This section of the codebase is owned by @madskristensen and |
Member
|
Thanks |
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.
The current pubspec.yaml schema requires topics to be at least 3 characters long:
But the
uitopic is valid and also popular with 369 packages including first-party Flutter packages: https://pub.dev/packages?q=topic%3AuiI've just modified the regex to accept 2 letter topics.