william chang(張仲威)

Results 129 comments of william chang(張仲威)

hi @stilren Yes, currently, GQLify simply exposes your database as an API. For user-based application or role-based access control application, it's best practice to separate an authentication layer (using `graphql-middleware`)...

@jthegedus the authentication directives will not be data-source specific, thus, it will not generate firestore security rules. It's going to create graphql middleware with the specified authentication rules and apply...

@ansarizafar Nice! Thanks for the information. Feel free to chime in with more opinions if you want. The feedback and opinions from you guys really matter to us in order...

@ansarizafar Thanks for the feedback! As for `aggregation queries`, we're already on our way to implement relay style queries. Follow up on this feature at https://github.com/Canner/gqlify/issues/9. As for `data validation...

Hi @jthegedus Currently, I only plan to implement `graphql-rbac` at our next release, but I did think about malicious queries protection before. Since most of them are apollo schema directives,...

In `v3.0.0`(https://github.com/Canner/gqlify/releases/tag/v3.0.0), we add `set` field to array field of create/update mutation. ## Change ### Create mutation #### Before ```graphql createUser(data: { members: [{name: 'wwwy3y3'}] }) {...} ``` #### After...

@jonesnc haven't check out Django api on the relationship before. Looks like we can actually use similar arguments on the cascade deletes part. Thanks for the helpful information!

@jthegedus At this stage, we haven't discussed much how GraphQL subscription API should be. There are many things we need to think through before implementing subscription, such as: * What...

@jthegedus Wow! Thanks for the detailed information! IMO, in GQLify, `@GQLifyModel` defines a **root level data-model**, so maybe we can introduce different directive like `GQLifySubResource`. It can work for [`Embedded...

Well, regarding the naming convention, I doubt anyone would put subcollection so nested (ex: `createAuthorInIssueThreadCommentSubcomment`) that it becomes a problem. If it really becomes a problem, we can always add...