Add asNonEmptyTuple
config option for typescript-enum-array
plugin
#1249
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.
Description
Description already discussed in my issue. The goal is to have a traceable, zod-compatible array declaration by allowing us to generate arrays with non-empty tuple type declarations.
as const
lets us use the arrays inzod
enums, but will show the enum declaration as a raw, unnamed string union. This makes it tougher in large codebases to trace the origins of the parsed zod schemas.Related #1243
Type of change
Please delete options that are not relevant.
Screenshots/Sandbox (if appropriate/relevant):
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can
reproduce. Please also list any relevant details for your test configuration
packages/plugins/typescript/enum-array/tests/enum-array.spec.ts
withasNonEmptyTuple
Checklist:
CONTRIBUTING doc and the
style guidelines of this project