-
-
Notifications
You must be signed in to change notification settings - Fork 674
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
Towards release 1.0 #623
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
@MichalLytek I upgraded, and everything worked just fine for me. I had been on the 0.18 beta releases. Great work! I guess |
Awesome stuff! Keep up the great work! Scott |
Awesome, will try it on my current project! |
Yesterday, Please give the |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
hi, Don't know if this issue is related to rc2 or to the graphql V15.0.0 Good job anyway, thks a lot |
@jeromeSH26 please isolate the issue and create a minimal reproducible code example |
here is a simplifed example (most of the interfaces and objects are in different files, I have put then all together for the example)
error : |
@jeromemeichelbeck Looks like it might be related to #373 and I don't have an idea how to solve that issue properly 😕 |
maybe, but it's weird because it was working fine before. I will try to downgrade graphql and/or type-graphql to find which one create this regression. it's not a big deal however although it reduces the scope of inheritance for large or shared librairies. |
Going from RC2 to RC3 uncovered some hidden errors in my entity definitions that took a bit of head scratching to find. I had defined a field as |
@mqdeandrade Thanks for sharing this info. |
graphql-subscriptions which type-graphql v1-rc3 relies on does not support graphql v15. Fresh I get a warning They have an open issue for graphl v15 support from April 2nd, still unresolved. apollographql/graphql-subscriptions#221 Perhaps type-graphql should stick with graphql v14 for now? Or can I safely ignore this warning? |
@ofbeaton Yes, you can safely ignore this warning - breaking changes in v15 were really small and minor, all my test suite with subscriptions work without any issues with v15 😉 |
TypeGraphQL 1.0 has been finally released! 🎉 You can read full changelog here: Thank you guys for the amazing support! ❤️ |
Today, I released the first Release Candidate version of major
1.0.0
🎉https://www.npmjs.com/package/type-graphql/v/1.0.0-rc.1
It is also distributed as a new major version on the default
latest
tag.This release contains a lot of breaking changes, so please read the release notes carefully 👀
https://github.com/MichalLytek/type-graphql/releases/tag/v1.0.0-rc.1
The 1.0.0 milestone is finished in 97% - it contains of 87 closed issues! 😵☺️
https://github.com/MichalLytek/type-graphql/milestone/3
The work that has to be also done before final release is to write the announcement post about the 1.0.0 release, after 2 years of developing TypeGraphQL
Feel free to update your apps and let me know how the new version works for you and what improvements you would like to see in the upcoming
1.0.0
release!And don't forget to support the project as its ongoing development is possible only thanks to the support by the community ❤️
Especially if you are using it commercially - just to ensure that the project which your product relies on is actively maintained and improved 💪
The text was updated successfully, but these errors were encountered: