Open
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
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.
Feature
Introduces a
hiddenboolean property to theSchemaclass, parsing theschema/hiddenconfiguration fromschema.yaml. This establishes a standardized parameter for frontend applications to query.Additional Info
Currently, it is a common practice for users to create "pseudo-schemas name" (伪方案) simply to mount dictionaries or serve as base dependencies for other schemas. Because frontends typically read and display all available schemas, these dependency-only schemas unnecessarily clutter the user's selection menu.
By introducing a
schema/hidden: trueflag, we provide an elegant, official convention for frontend developers to filter out these non-interactive schemas, eliminating the need for traditional, hacky workarounds.