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
Is your feature request related to a problem? Please describe.
The new GraphQL feature help developers to collaborate due to the self documented API. It's really helpful for other developers (like front-developers) to work with faked data trough GraphQL.
Describe the solution you'd like
I think it would be interesting to integrate a data faker system directly in parse server to ease the local development. We can use a code first strategy via: JS Schema Doc.
Describe alternatives you've considered
Use an external project like GraphQL Faker but this is a schema first strategy and it's not really helpful when working with GraphQL Parse Server
Additional context
I'm here to discuss about the system. I can begin a PR if we validate the concept ! 🚀
The text was updated successfully, but these errors were encountered:
I like the idea, but it is not so clear for me how it would work. Could you detail how you imagine it working in Parse Server? I mean, how this data would be set, how the developers would choose for the fake data or not...
Is your feature request related to a problem? Please describe.
The new GraphQL feature help developers to collaborate due to the self documented API. It's really helpful for other developers (like front-developers) to work with faked data trough GraphQL.
Describe the solution you'd like
I think it would be interesting to integrate a data faker system directly in parse server to ease the local development. We can use a
code first
strategy via: JS Schema Doc.Describe alternatives you've considered
Use an external project like GraphQL Faker but this is a
schema first
strategy and it's not really helpful when working withGraphQL Parse Server
Additional context
I'm here to discuss about the system. I can begin a PR if we validate the concept ! 🚀
The text was updated successfully, but these errors were encountered: