NOT FOR RELEASE VERSION
When doing multiple methods or properties, some questions have the same answer between members. Why not use the last-provided answer as the default for the current one, provided there is not a default in the questions file.
- Build should process partials and callbacks.
- Interface should handle callbacks. (Currently a dummy value must be entered for -n because a single un-interfaced function cannot be entered.)
- Build should validate Kuma macros and API identifiers. For kuma macros that generate cross-references, it should ping the url. If 404 comes back, it should search for the IDL and ask appropriate questions.
- Build should fill in questions that can be answered from the IDL such as whether there's a constructor or whether something is read-only.
- Make template processing recursive and based on common sections. For example
reference.html
>_frag_properties.html
>_frag_property.html
. - Output BCD boilerplate for entry and remaining build commands.
- The prompt for
APIRef()
should display possible values fromGroupData.json
. - The prompt for the
APIRef()
macro should invoke a check that it exists inGroupData.json
. - The prompt for
SpecName()
should behave the same as for `APIRef()' - The
find
andbuild
commands should be able to search on interface members.
Here's an approach to meta-configuration such as logging and test mode. (Approach is about 1/3 down the page.)
-
Change
shared:formalAPIName
toshared:apiName
throughout. Anywhere that it should be suffixed with 'API' add it to the template. Give this a follow-up task that ensures it's not present twice. -
Deal more completely with inheritance.
JavaScript built-ins: https://cs.chromium.org/codesearch/f/chromium/src/v8/src/builtins/builtins-definitions.h?cl=HEAD