We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rose configurations support a couple of odd features which don't have direct mappings onto JSON Schema.
We need a proposal for how to support these in a schema driven GUI.
Rose configs have one of three orthogonal states:
!
!!
x
The current rose edit allows users to change the state of configs live.
rose edit
Just to muddy the waters, sections can be ignored too with the ^ prefix.
^
In Rose comments are functional, they are displayed and are editable in the GUI.
Example of Rose comment for the configuration [env]FOO in a rose-app.conf file:
[env]FOO
rose-app.conf
[env] # bodge to keep the universe from collapsing in a puff of logic ANSWER=42
Comments look like metadata, but they are part of the configuration.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Rose configurations support a couple of odd features which don't have direct mappings onto JSON Schema.
We need a proposal for how to support these in a schema driven GUI.
States
Rose configs have one of three orthogonal states:
!
) - Config has been ignored by the user (i.e. manual intervention)!!
) - Config has been ignored by metadata logic (e.g. this config is not needed because another is set tox
)The current
rose edit
allows users to change the state of configs live.Just to muddy the waters, sections can be ignored too with the
^
prefix.Comments
In Rose comments are functional, they are displayed and are editable in the GUI.
Example of Rose comment for the configuration
[env]FOO
in arose-app.conf
file:Comments look like metadata, but they are part of the configuration.
The text was updated successfully, but these errors were encountered: