Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

eslint: add the no-wrapper-object-types rule #868

Merged
merged 2 commits into from
Dec 15, 2024

Conversation

sguimmara
Copy link
Contributor

This rule disallow so-called wrapper types in favor of primitives types: boolean instead of Boolean, number instead of Number, etc.

The official Typescript documentation says:

The type names String, Number, and Boolean (starting with capital letters) are legal, but refer to some special built-in types that will very rarely appear in your code. Always use string, number, or boolean for types.

@gkjohnson
Copy link
Contributor

Great thank you! This is a good rule to have - I wasn't aware of the diffrence.

@gkjohnson gkjohnson merged commit f230d98 into NASA-AMMOS:master Dec 15, 2024
2 checks passed
@gkjohnson gkjohnson added this to the v0.3.46 milestone Dec 15, 2024
@sguimmara sguimmara deleted the typescript-eslint branch December 24, 2024 16:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants