`nexus-prisma` is handed over to the community for more active maintenance & future development 🚀 about nexus-prisma HOT 8 OPEN

Thank you @nikolasburk for the introduction. I’d like to continue on maintenance on nexus-prisma for two specific reasons.

• To support existing users of nexus nexus-prisma, who don’t have the capacity to migrate to very promising alternatives such as Pothos, and TypeGraphQL
• To keep pace for nexus with prisma updates. This is still important for nexus users, who prefer the nexus concept of types generation.

As @nikolasburk has mentioned I’d like to prioritize first regular cuts of releases, and then look into current issues.

from nexus-prisma.

@Frosty21 yes, sure I'm gonna look this weekend at how we could enable automatic releases for minor, patch chore(deps).

from nexus-prisma.

@rostislav-simonik I'd love to join the repository contributors. Been helping the Prisma team to progress a lot with this package last summer.

from nexus-prisma.

@iddan that's good news, I wrote a suggestion for roadmap #306, feel free to review and suggest anything you wish. If you are ok to deal chore(deps) first you can start on that, I'll give you access. I'm interested in PR reviews, but if everything passes, and I won't respond within 24 hours, you can self-approve, and merge them as well.

from nexus-prisma.

Congrats @rostislav-simonik if there is anything I can do to help out let me know.

• I think first thing we should be addressing is chore(deps) in hand at the moment.
• Then look into improving the documentation (I'll look into helping here)

from nexus-prisma.

This is great news. I think Nexus is a great framework and its too bad support ended. Nexus-Prisma has saved countless hours and is an amazing bit of code!

from nexus-prisma.

@medet-mattr I made some progress two weeks ago but got temporarily busy with something else, I'm planning to make some progress next week.

from nexus-prisma.

hi, any updates on nexus-prisms?

from nexus-prisma.