V2: Update documentation for plugin options import_extension and ts_nocheck #413
Conversation
This file contains hidden or 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
Signed-off-by: Timo Stamm <ts@timostamm.de>
smaye81
approved these changes
Sep 24, 2024
timostamm
deleted the
tstamm/Update-documentation-for-plugin-options-import_extension-and-ts_nocheck
branch
Merged
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.
With version 2 of @bufbuild/protoplugin, standard plugin options have more convenient default behavior:
import_extensionis nownoneby default, which means we don't add a.jsextension to importpaths. If you use the plugin option
import_extension=none, you can delete it. If you require imports to have the.jsextension, use
import_extension=js.ts_nocheckis now off by default. If you require a// @ts-nocheckannotation at the top ofgenerated code, use
ts_nocheck=true.