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
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
The text was updated successfully, but these errors were encountered:
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 cachedThe text was updated successfully, but these errors were encountered: