-
Notifications
You must be signed in to change notification settings - Fork 162
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
Define definition conventions #882
Conversation
... Helps with #730.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other places to update:
- "To invoke the toJSON() operation of the Transaction interface, run the following steps:"
- "Thus, prose is required to explain the stringification behavior, such as the following paragraph:" we didn't define a convention here, but maybe we should
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a bit unsure about introducing the separate concept of "getter description" vs. "getter steps". Maybe instead a phrasing like
The getter steps of an attribute attr should be introduced using text of the form "The ...", or text of the form "The ..." followed by an inline description.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks ok to me.
There's still a number of inconsistencies here with regard to whether or not this is explicitly passed in. If someone more familiar with all this could add fixup commits that'd be appreciated or we could leave them as existing issues and file a follow-up. |
I gave it a shot; please take a look! |
This looks great to me. @EdgarChen and @TimothyGu interested in giving this a final review? |
Nice cleanups :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice catch on the other places to use "method steps", @annevk. I fixed them further by always passing a this value, and using list notation for the argument lists.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pushed another commit with some minor consistency fixes, but still LGTM.
Aligns with whatwg/webidl#882: - Describe getters as "The attr getter steps are [...]". - Describe methods as "The myMethod(arg) method steps are [...]".
Aligns with whatwg/webidl#882: - Describe getters as "The attr getter steps are [...]". - Describe methods as "The myMethod(arg) method steps are [...]".
…rs. (#49) Aligns with whatwg/webidl#882: - Describe getters as "The attr getter steps are [...]". - Describe methods as "The myMethod(arg) method steps are [...]".
…rs. (#330) Aligns with whatwg/webidl#882: - Describe getters as "The attr getter steps are [...]". - Describe methods as "The myMethod(arg) method steps are [...]".
- Use Web IDL's definition conventions for methods and getters (whatwg/webidl#882): - Describe getters as "The attr getter steps are [...]". - Describe methods as "The myMethod(arg) method steps are [...]". - Refer to [=this=] as defined in Web IDL rather than a concept that was not defined anywhere. - Use [=this=] rather than the `sensor_instance` variable where possible, as the latter was not defined anywhere. - When invoking the "notify error" abstract operation, pass the arguments in the order expected by the operation.
- Use Web IDL's definition conventions for methods and getters (whatwg/webidl#882): - Describe getters as "The attr getter steps are [...]". - Describe methods as "The myMethod(arg) method steps are [...]". - Refer to [=this=] as defined in Web IDL rather than a concept that was not defined anywhere. - Use [=this=] rather than the `sensor_instance` variable where possible, as the latter was not defined anywhere. - When invoking the "notify error" abstract operation, pass the arguments in the order expected by the operation.
- Use Web IDL's definition conventions for methods and getters (whatwg/webidl#882): - Describe getters as "The attr getter steps are [...]". - Describe methods as "The myMethod(arg) method steps are [...]". - Refer to [=this=] as defined in Web IDL rather than a concept that was not defined anywhere. - Use [=this=] rather than the `sensor_instance` variable where possible, as the latter was not defined anywhere. - When invoking the "notify error" abstract operation, pass the arguments in the order expected by the operation.
Aligns with whatwg/webidl#882 and uses the format "The _attr_ getter steps are [...]".
Aligns with whatwg/webidl#882 and uses the format "The _attr_ getter steps are [...]".
...
Helps with #730.
Preview | Diff