-
Notifications
You must be signed in to change notification settings - Fork 32
Add documentation for types and their members #122
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
Comments
Another thing I'd really like to see is surfacing browser support or baseline information on the API docs. This past week they adjusted the baseline definition to have "Newly available" and "Widely available" as well. They have an npm package to access this data. Eventually this could even be used to add something like support metadata/annotations to the generated members. Then we could have a lint (or similar) that triggers on any unguarded usage of an API that's not in the "Widely available" category, or at least "Newly available". |
The data from the |
This is mostly done; we can track remaining work / improvements in more specific issues (eg. #190). |
We should likely fetch data from the MDN and auto-annotate IDL types.
The text was updated successfully, but these errors were encountered: