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
I love this way of showing usages and needs of patterns and API:s.
Great resource for people trying out the alpha and for dev-rel to learn how to use it.
Not sure of you want my view on the new pieces of the API (and the typedefs), but here they come :)
Not sure about the @timestamps directive. Or to be more precise, I'm not sure about the implicit part where they add fields automatically. It's certainly convenient for the developer though, so I'm a bit torn.
@readonly on the password seems wrong in a real world app.
Not a big fan of canEdit and canDelete being root level fields on the Post, it would make more sense to have a PostPermissions type on a permissions field on the Post instead. But that might be hard to do?
The showcase of the OGM in signUp and signIn is great 👍
Great to see the visualization from Arrows.
You're doing crazy good work 🎄
The text was updated successfully, but these errors were encountered:
@oskarhane Hello & thank you for taking a look. Great to see your opinions :) 🎄
I completely agree with you on the implicitness of the @timestamps directive. It auto-populates properties createdAt & updatedAt. While being common properties, for library implementing timestamps, they still pose a barrier to entry. I quickly settled on the current implementation, completely open to discussion, as I deemed timestamps something necessary to showcase a 'real world like' application.
Good spot on the password @readonly I forgot to mention about the just added section to the README here
Your comments on canEdit and canDelete are really valuable because i tried to implement your suggestion;
Unforchunetly it dont work as intended just yet & neither does it in neo4j-graphql-js. Something we should implement in the near future. I feel it would work well with ignored directives because we may not want users creating PostPermissions nodes in the database.
This is fantastic @danstarns!
I love this way of showing usages and needs of patterns and API:s.
Great resource for people trying out the alpha and for dev-rel to learn how to use it.
Not sure of you want my view on the new pieces of the API (and the typedefs), but here they come :)
@timestamps
directive. Or to be more precise, I'm not sure about the implicit part where they add fields automatically. It's certainly convenient for the developer though, so I'm a bit torn.@readonly
on the password seems wrong in a real world app.canEdit
andcanDelete
being root level fields on the Post, it would make more sense to have aPostPermissions
type on apermissions
field on the Post instead. But that might be hard to do?signUp
andsignIn
is great 👍The text was updated successfully, but these errors were encountered: