Fix documentation bugs (formats) #790
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I just realized there's one more thing that needs fixing, the parameters table for |
|
New commit pushed to fix the rendering of the parameter list for getTypeScriptType I've updated the image in my original post to reflect the changes |
dbanksdesign
approved these changes
Mar 29, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available:
Description of changes:
Fixes to documentation:
getTypeScriptTypesection in format configurationBefore
After (previewing of markdown in Visual Studio after running
npm run generate-docs)Not sure if I should include the generated
.docs/formats.mdin this PR... but I guess it will be overwritten anyway when building the release, right?By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.