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
In a few hours I want to start a project with this.
Issues
Copying the code from the Readme for convert_plugin.go I have to write an additional argument for gbgen.NewConvertPlugin. What should I write there?
Proposals
I undertake to write documentation for every single thing I learn, day after day: explanations that maybe those who created it take for granted, recipes for routine things etc.
But we have to decide where to write them: one thing that doesn't steal more than 10 minutes of setup. A Gitbook on github pages?
Fears
How to write business logic after all the generation?
Example:
If I'm creating a Player for a Team I wanna check if Team has enough "space" before (in a simple DB transaction).
Is this eventuality considered? I think so, of course. I just don't know where to start. 😢
Have you ever needed to use something for tenants in the DB?
The next step in this project to add option for custom resolvers and custom converts so we can re-generate without loosing the custom things. But I'm a little short on time.
e.g. if you have a function name UserToGraphql in your package and it's not in the default files we will generate UserToGraphqlOriginal which you can still use but your custom function is getting called.
Yes but it's really stupid now since it's hardcoded automatically on userId and organizationId this needs to be customizable I only made it work for my own use case. It's also a requirement for security to add these field to every table out there + I need a solution for admin calls where the userId would need to be provided sometimes
Your work is amazing!
It feels like every line of code is sweaty. 😄
A huge thank you for all this.
In a few hours I want to start a project with this.
Issues
convert_plugin.go
I have to write an additional argument forgbgen.NewConvertPlugin
. What should I write there?Proposals
I undertake to write documentation for every single thing I learn, day after day: explanations that maybe those who created it take for granted, recipes for routine things etc.
But we have to decide where to write them: one thing that doesn't steal more than 10 minutes of setup. A Gitbook on github pages?
Fears
How to write business logic after all the generation?
Example:
If I'm creating a Player for a Team I wanna check if Team has enough "space" before (in a simple DB transaction).
Is this eventuality considered? I think so, of course. I just don't know where to start. 😢
Have you ever needed to use something for tenants in the DB?
Something like https://github.com/influitive/apartment for Rails.
Quite simply adding
WHERE tenant_id = [ID]
to each DB query and the same for insert/update/delete queries.Thanks again for this huge huge huge work! 😄
The text was updated successfully, but these errors were encountered: