typings for defaultless settings#512
Merged
Merged
Conversation
Contributor
Author
|
@Captain8771 can you review as well |
Contributor
|
(i have no clue what is good practice in typing) |
Vendicated
reviewed
Feb 28, 2023
Vendicated
reviewed
Feb 28, 2023
Contributor
Author
|
yop |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
this adds real typings for settings definitions that dont have a
defaultfield:COMPONENTtypes are still alwaysanySELECTtypes areT | undefinedif there are no{ default: boolean }elementsT | undefinedif there is no default field