-
Notifications
You must be signed in to change notification settings - Fork 154
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 fields #2123
Comments
Taking up |
@kddnewton We can actually mark the nodes which doesn't have any fields as done right? |
Yes you're right, I just marked them all as completed. |
- Adds documentation for the fields of the `IfNode`. Also updates the overall description to mention ternary expressions. - Part of ruby#2123
@kddnewton calling dibs on ArrayNode |
That one already has an open PR. But the others should be good! |
Should've looked at the PRs too. Taking PR: #2214 |
Taking PR: #2216 |
Taking |
- Adds documentation for the fields of the `IfNode`. Also updates the overall description to mention ternary expressions. - Part of ruby#2123
- Adds documentation for the fields of the `IfNode`. Also updates the overall description to mention ternary expressions. - Part of ruby#2123
Partially fixes: ruby#2123
At the moment, our
config.yml
file has documentation for every node type in the syntax tree. However, there is little to no documentation for the individual fields on the nodes. This is a crucial piece of information for understanding how the nodes should be used and what they represent. Therefore, we would like to document each field on each node, and surface that documentation to the end user.This issue serves as a meta-issue for that work. Each node is listed below, and should be checked off when all of its fields are completely documented.
In terms of style we are very much not looking for "this is the receiver of the method call". Instead we are looking for "this can be
nil
or a node that represents a non-void expression". Generally we want to avoid tautological statements, and instead favor more useful comments. Examples are encouraged — where applicable — and should begin with 4 spaces. Seeprism/config.yml
Lines 717 to 729 in c790abd
For determining which are documented, run:
The text was updated successfully, but these errors were encountered: