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
TypeScript compiler changes have a huge impact on pact-gen-ts functionality. Due to TS not following semantic versioning it is hard to predict when it might cause issues with pact-gen-ts library.
Closing issue after coming to a conclusion that this will not make maintenance easier. Having the knowledge in advance that pact-gen-ts will not work with new TypeScript version will not allow to react and fix the issue sooner. It is because most of the fixes require ts-morph update so we still have to wait for it and only after that, pact-gen-ts can be aligned with news TS version.
TypeScript compiler changes have a huge impact on pact-gen-ts functionality. Due to TS not following semantic versioning it is hard to predict when it might cause issues with pact-gen-ts library.
My suggestion is to test library with different versions of TypeScript - including @next. Example implementation provided here: react-redux gh action with different TS versions.
It could give us quick feedback whether the API changed in upcomfing TypeScript version
The text was updated successfully, but these errors were encountered: