You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
In 2022 we encountered a few nasty edge-case-y-TypeScript-issues related to some specific TypeScript versions (partly because TypeScript is complex and doesn't strictly follow SemVer)
Since this package is the only one with critical types, I don't think it's worth the overhead to port this solution to other SDKs or the template for now (or maybe just React/Vue)
Is your feature request related to a problem? Please describe.
In 2022 we encountered a few nasty edge-case-y-TypeScript-issues related to some specific TypeScript versions (partly because TypeScript is complex and doesn't strictly follow SemVer)
Describe the solution you'd like
To attempt to catch those issues early we could update the CI to run type tests against various TypeScript versions.
zod
does so following a matrix strategy for example: https://github.com/colinhacks/zod/blob/master/.github/workflows/test.yml#L11-L27Since this package is the only one with critical types, I don't think it's worth the overhead to port this solution to other SDKs or the template for now (or maybe just React/Vue)
Describe alternatives you've considered
Doing nothing is a also valid option 🤷♀️
Additional context
In an attempt to mitigate these issues we already started to systematically type check our projects as part of our test suite, e.g. https://github.com/prismicio/prismic-client/blob/v7/package.json#L49
The text was updated successfully, but these errors were encountered: