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
We want to cache the results of parse & validate for queries sent to our service. On subsequent requests, we would like to avoid re-validating the cached parsed query. This bit of code in runQuery always runs all the default validation rules, leaving us unable to leverage it on subsequent requests without doing an unnecessary revalidation. The comment above that code snippet describes our desired behavior, but the implementation itself seems to not.
Is there a way to circumvent this? If not, is this something that can be added or adjusted? Happy to submit a PR if needed. Thanks.
The text was updated successfully, but these errors were encountered:
Hi, hoping this can get some traction now that we're past the holiday. I noticed that this comment, as well, indicates different behavior than what is actually happening. Again, just let me know what you'd like to see in a PR for this one and I'll get it together. Thank you.
We want to cache the results of parse & validate for queries sent to our service. On subsequent requests, we would like to avoid re-validating the cached parsed query. This bit of code in
runQuery
always runs all the default validation rules, leaving us unable to leverage it on subsequent requests without doing an unnecessary revalidation. The comment above that code snippet describes our desired behavior, but the implementation itself seems to not.Is there a way to circumvent this? If not, is this something that can be added or adjusted? Happy to submit a PR if needed. Thanks.
The text was updated successfully, but these errors were encountered: