No native utility types validation lint#4567
Merged
Conversation
flobernd
reviewed
Jun 13, 2025
Member
flobernd
left a comment
There was a problem hiding this comment.
Let's see if we can find a way to do this generically if possible. There are more types we want to avoid (e.g. Map).
Besides that we have builtins like "any" that should be disallowed and dictionary-like syntax contexts like:
{ [id: string] : SomeType; }
This is one of the harder validations and we can only try to make a best effort here. It probably wont ever be exhaustive.
Contributor
|
Following you can find the validation changes against the target branch for the APIs. No changes detected. You can validate these APIs yourself by using the |
pquentin
approved these changes
Aug 12, 2025
Member
pquentin
left a comment
There was a problem hiding this comment.
Merging as this is a good first step.
szybia
added a commit
that referenced
this pull request
Aug 12, 2025
* origin/main: [DOCS] Fix typos in the shared overlays file (#5124) Update specification output Remove unused EIS types (#5107) No native utility types validation lint (#4567) Document reindexing failures (#5031) Add dangling types to validation-errors.json (#5106) Update specification output Change `KeyedPercentiles` value type from `long` to `double` (#5108) [DOCS]: Add descriptions to API tags (#5098) Bump form-data and @redocly/cli in /docs/examples (#5074) Update specification output Adds cat-h values (#5096) Bump @eslint/plugin-kit from 0.3.3 to 0.3.4 in /specification (#5053) Update specification output [DOCS] Adds Ruby bulk helper to BulkRequest documentation (#5057)
pquentin
pushed a commit
that referenced
this pull request
Nov 7, 2025
* hardcoded rule * a bit less hardcoded (still) * test (cherry picked from commit 26fdeef)
Member
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
pquentin
added a commit
that referenced
this pull request
Nov 7, 2025
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
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.
To prevent the use of types such as Record, in favor of our aliases (e.g. Dictionary).
Originally this had to be less hardcoded and more about checking if a type was imported from our modules or from the typescript standard library, but so far I found no ways of achieving so.