New issue
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
Document what attributes control what in one place #149
Comments
A (full?) list of attributes that should be documented:
|
See also:
|
Here's a start:
|
Create a new table
Where attr is the name of the attribute and doc is the doc text for usage. The doc text is set from the add attr commands (add a doc=) flag. This way users can document their own attributes and by keeping this in another table we avoid the scoping stuff and treat all attributes as reserved words (meanings they have the same semantics at all scopes). |
Since it's a DB change, I'm suggesting this goes into 5.0 |
…es not yet add the actual documentation. See stacki #149 for a rough draft of that documentation
The database table and relevant commands for interacting with it went into 8070e1d. The actual default documentation strings (which should probably land in a node XML file?) did not land yet. See above for a start, but it is still TODO. |
The branch |
There are a number of attributes that have meaning at different levels (for example, kickstartable, managed, etc). These should be documented in one place with a description of what they control and when they should be set.
The text was updated successfully, but these errors were encountered: