feat: no null/undefined in template literal #246
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
WillieRuemmele
approved these changes
Jun 27, 2024
mdonnalley
approved these changes
Jun 27, 2024
cristiand391
approved these changes
Jun 27, 2024
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.
shipping
undefinedandnullin template literals is bad. ex:oclif/plugin-update#855
wouldn't you like the compiler to tell you when you're exposing us to that?
@W-16115298@
to run green, this requires
salesforcecli/plugin-apex#506
forcedotcom/source-tracking#622
salesforcecli/plugin-info#789
salesforcecli/plugin-custom-metadata#868
salesforcecli/plugin-dev#516
salesforcecli/plugin-deploy-retrieve#1093