Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

gqlGen migration #13

Open
NoBypass opened this issue Oct 10, 2023 · 0 comments
Open

gqlGen migration #13

NoBypass opened this issue Oct 10, 2023 · 0 comments
Assignees
@NoBypass
Labels
backend Backend related change Change idea of existing feature

Comments

@NoBypass
Copy link
Owner

Description
Instead of using the self written generator, gqlGen should be used. It allows for easier implementation of everything graphql-related. Authentication and caching can also be easily done with it.

Impact
It will mostly be a DX improvement.

Optional: Technical Description
The biggest technical challenge will most likely be the mapping from a neo4j result to graphql.
@NoBypass NoBypass added backend Backend related change Change idea of existing feature labels Oct 10, 2023
@NoBypass NoBypass self-assigned this Oct 10, 2023
@NoBypass NoBypass added this to FDS Oct 10, 2023
@NoBypass NoBypass moved this to In Progress in FDS Oct 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@NoBypass NoBypass

Labels
backend Backend related change Change idea of existing feature
Projects
FDS
Status: In Progress
Milestone
No milestone
Development

No branches or pull requests
1 participant
@NoBypass