[PR#5468] refactor: remove TypeScript non null assertions #5518
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.
📑 Summary
Note
This PR does not target the
develop
branch. Instead it targets:I'm not a big fan of using TypeScript's non-null assertion operator (e.g.
map.get(val)!
).Instead, I've tried to rewrite the code when possible, so it's not needed. E.g., instead of doing:
I've tried to do things that TypeScript can understand, e.g.
There's also some other misc improvements I found when reviewing #5468.
There should be no functional changes to the code, this is a refactoring only change.
📏 Design Decisions
Describe the way your implementation works or what design decisions you made if applicable.
📋 Tasks
Make sure you
MERMAID_RELEASE_VERSION
is used for all new features.develop
branch