fix: advise people of the ESLint Plugin for catching interpolation issues #15854
+4
−1
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
AaronFriel
added
the
impact/no-changelog-required
Changelog[uncommitted] (2024-04-02) |
AaronFriel
requested review from
a team
and removed request for
a team,
lunaris and
justinvp
lunaris
approved these changes
Jun 21, 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.
Raised by @lunaris in onboarding, we don't advertise the Pulumi ESLint Plugin. As using an output in a template literal is one of the most common avenues to discovering this issue, perhaps we should advertise the plugin here?
What's lacking from this is documentation, but I imagine that users will see this, create issues, and that will drive improvements either in the base SDK or the ESLint Plugin.