308
edits
(Add some suggestions from annevk to spec sanity section) |
(Add a thing about intents to implement.) |
||
Line 11: | Line 11: | ||
* The API should be easy to understand and use, and consistent. | * The API should be easy to understand and use, and consistent. | ||
* There should be an intent to implement for the feature, and the reviewer should not be objecting to the intent. In particular, this means checking whether other UAs plan to implement this spec, and if not why we're doing it. | |||
* Whether things are nullable or not needs to make sense. | * Whether things are nullable or not needs to make sense. | ||
* Whether arguments and dictionary members are optional or not needs to make sense. | * Whether arguments and dictionary members are optional or not needs to make sense. |
edits