Strict mode troubleshooting #3625
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
offlineprogrammer
approved these changes
Sep 28, 2021
wlee221
commented
Sep 28, 2021
added 3 commits
September 30, 2021 10:18
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: #2918, #3140, #3376, stackoverflow
Description of changes: This adds troubleshooting section for using Typescript strict mode. This is prominent on Angular 12+ users as Angular 12 turns on strict mode by default, but this is relevant to all users who uses stricter TypeScript settings. I pulled it out to a separate troubleshooting for that reason, and we can reference this document from issues and UI docs as well.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.