Skip to content

fix: Support for type operators readonly & unique (#1336) #1354

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

Closed
wants to merge 6 commits into from
Closed

fix: Support for type operators readonly & unique (#1336) #1354

wants to merge 6 commits into from

Conversation

ericzhangjx
Copy link
Contributor

Fixes #1336

BTW although all tests passed, I found no test files for converter/types/type-operator.ts or models/type/type-operator.ts. I can only use the built package to generate docs for my working project (and confirmed the correctness). Maybe a revision of tests should also be involved.

@Gerrit0
Copy link
Collaborator

Gerrit0 commented Aug 23, 2020

Looks good! I would like to have a test

  • Add a new file in src/test/converter/types for type operators
  • Export some types which use these operators
  • Rebuild the specs with npm run rebuild_specs converter types

@ericzhangjx
Copy link
Contributor Author

Test cases for type operators unique, readonly and keyof added (much easier than I thought!)

@ericzhangjx
Copy link
Contributor Author

Okay this looks weird... Some other commits are involved.
I'm thinking if I wrongly executed git pull typedoc master before adding test cases. Should I close this pr and open another one?

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.

readonly T[] is exported as keyof T[]
5 participants