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.

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

Cached parameters on deployment #365

Open
loopingz opened this issue Mar 18, 2023 · 0 comments
Open

Cached parameters on deployment #365

loopingz opened this issue Mar 18, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@loopingz
Copy link
Owner

GraphQLService will calculate the schema based on the application, this calculation once deployed will be the same as before, we should therefore have a mechanism for service to cache this type of calculation on deployment.

We could use the getParameters() of service to store the processed parameters to then store it in the webda.config.json.
This would mean a initialization like this.schema ??= this.generateSchema(...) would only be called when not cached

@loopingz loopingz added the enhancement New feature or request label Mar 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant