Skip to content

Conversation

@margaretjgu
Copy link
Member

Closes #4538

@github-actions
Copy link
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 make validate target.

`type MyReq = Required<string>`,
`type MyPick Pick<integer,"something">`,
`type MyOmit = Omit<Record, "something">`,
`type MyDict = Dictionary<string, object>`,
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The original test file had a bug...it included native types like Record, Partial, etc. in BOTH the valid and invalid arrays. This was contradictory and causing test failures.

I corrected the tests to properly reflect the rule's intent:

  • valid: Now uses spec-defined aliases (Dictionary) and allowed types (arrays, custom classes)
  • invalid: Contains native utility types (Record, Partial, etc.) and collection types (Map, Set, etc.)

also added test coverage for the new collection types (Map, Set, WeakMap, WeakSet).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[validation] Native typescript collection types should not be used

2 participants