Skip to content

Recommend Docs Authoring Pack extension and configure dev langs #1911

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

Merged

Conversation

scottaddie
Copy link
Contributor

Recommend the Docs Authoring Pack extension for contributors using VS Code. VS Code users who don't already have the extension installed will be asked if they want to install it.

The other part of this PR configures the docs-markdown extension that is bundled with Docs Authoring Pack. Commonly used dev langs for code snippets in the docset are presented to the user when typing 3 backticks (```). I came up with this list based on search results. See dotnet/AspNetCore.Docs#16986 for a preview of that functionality.

Copy link
Contributor

@colin-home colin-home left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@scottaddie
Thanks. I can't find any information on the "markdown.docsetLanguages" value or the list of languages. Is this documented somewhere?

@colin-home
Copy link
Contributor

@scottaddie
... said the man who forgot to keep reading your comment. D'oh!

@colin-home colin-home merged commit 071e56d into MicrosoftDocs:master Feb 14, 2020
@scottaddie
Copy link
Contributor Author

scottaddie commented Feb 14, 2020

@corob-msft The list of valid language identifiers can be found at https://github.com/microsoft/vscode-docs-authoring/blob/d9935e346f11a2aed7ed076e4d002526929b91cc/docs-markdown/src/helper/highlight-langs.ts#L42. If you modify the settings.json file in VS Code, a JSON schema provides IntelliSense to help you select the appropriate values.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants