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

fix: consistently use NeverType #1367

Merged
merged 2 commits into from
Aug 19, 2022
Merged

fix: consistently use NeverType #1367

merged 2 commits into from
Aug 19, 2022

Conversation

daanboer
Copy link
Contributor

Currently, the undefined keyword is used to represent the never type in provided TypeScript code. This is undesirable, as it can lead to some situations where the intended use of the keyword is ambiguous. Fortunately, #1154 added a NeverType, although it is only used marginally in the current version. As I previously mentioned in #1261, gradually switching to NeverType is hard, as it leads to regressions. Therefore, this pr aims to replace all affected occurrences of the undefined keyword with NeverType. Additionally, optional object properties with type never are now hidden by the ObjectTypeFormatter when additionalProperties is false.

@daanboer daanboer changed the title Consistently use NeverType fix: consistently use NeverType Aug 18, 2022
@domoritz
Copy link
Member

Very nice. Thank you!

@domoritz domoritz merged commit 3ded513 into vega:next Aug 19, 2022
@github-actions
Copy link

🚀 PR was released in v1.1.0 🚀

@github-actions github-actions bot added released This issue/pull request has been released. and removed prerelease labels Sep 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
released This issue/pull request has been released.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants