-
Notifications
You must be signed in to change notification settings - Fork 109
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
Link to MDN API docs from intellisense #12
Comments
Here's a way to grab the full directory of MDN's HTML reference: https://developer.mozilla.org/en-US/docs/Web/HTML/Element$children?expand By pulling that down, you can query the JSON for individual tag summaries and page URLs. FYI the payload also includes localized pages, so you'll want to account for that in your query. You can also form similar query strings for other areas: CSS DOM APIs JavaScript |
It may be a better idea to use the browser-compat-data repo to find documentation links for each HTML element. You can find the full list of elements at https://github.com/mdn/browser-compat-data/tree/master/html/elements The BCD is already used by the CSS language server and has been proposed to be used in #22 and #30. |
/cc @atopal |
Re @connorshea, this is something I talked to Mozilla about and look forward to adding. We'll most likely use mdn/data instead of mdn/browser-compat-data for this, and start from CSS. |
Changes: - Feature: HTML attribute completion documentation - Rename: tagProvider -> dataProvider - API: Now in sync with CSS LS API - HTMLTagSpecification converted to serializable plain data structure so does attributes and attribute values - Remove Angular1/Ionic1 support - Remove i18n for HTML tags, and manage them in a plain JSON-like file because - We don't have i18n support in LSP yet - There's no translation yet - The JSON-like file is typed and can be easily mainaintaed - We'll start pulling data from W3C HTML spec and MDN to do features such as short descriptions, browser support table adn syntax. Such plain JSON-like files are easy to auto-generate. - Unblocks #12, #30, #44 Fixes: - Fix microsoft/vscode#2784 - Part of microsoft/vscode#63955 (no CompletionItem.documentation for attr value yet)
Changes: - Feature: HTML attribute completion documentation - Rename: tagProvider -> dataProvider - API: Now in sync with CSS LS API - HTMLTagSpecification converted to serializable plain data structure so does attributes and attribute values - Remove Angular1/Ionic1 support - Remove i18n for HTML tags, and manage them in a plain JSON-like file because - We don't have i18n support in LSP yet - There's no translation yet - The JSON-like file is typed and can be easily mainaintaed - We'll start pulling data from W3C HTML spec and MDN to do features such as short descriptions, browser support table adn syntax. Such plain JSON-like files are easy to auto-generate. - Unblocks #12, #30, #44 Fixes: - Fix microsoft/vscode#2784 - Part of microsoft/vscode#63955 (no CompletionItem.documentation for attr value yet)
Add back links and refer to MDN. FIx #12
That's really awesome @octref! Many thanks for this. I was wondering if we could add a URL parameter, so we can see on the MDN side when requests come from this? It helps us justify spending time on our "make MDN content available outside of MDN" efforts when we can demonstrate usage and we can optimize content for this usage in the future. Either way: really happy to see this :) |
From @Tyriar on February 23, 2016 17:10
It would be very convenient to have links to API documentation (MDN?) directly within intellisense for HTML, CSS and JS.
(Currently HTML descriptions is pulled from the spec)
Copied from original issue: microsoft/vscode#3358
The text was updated successfully, but these errors were encountered: