Open benmccallum opened 1 year ago
Right now I've set the config files to use Default and am updating them to use PersistedQuery as part of our build process (not the worst solution to be honest, but not as easy to debug :P).
Default is ideal on localhost as I don't want to be pushing new queries up to redis while developin (we do that in our build pipeline too).
Is there an existing issue for this?
Product
Strawberry Shake
Describe the bug
Seems to be now that the
CSharpGenerator
respects thesettings.RequestStrategy
(coming from the .graphqlrc file direct?) rather than being influenced by any of the MSBuild properties that influence the writing of the persisted query file to the query output directory.Before (v12): If you didn't specify
GraphQLPersistedQueryOutput
property (default is""
) nor theGraphQLPersistedQueryFormat
(default is"default"
), even if your .graphqlrc.json file specified thePersistedQuery
strategy, you:This was great because you could do the following to run without persisted queries during Development.
Now (v13):
It feels like these two things should operate the same. For now, the only way to get different behaviour between Debug and Release builds would be to edit the .graphqlrc file on the fly, right?
To restore the old behaviour, it might be best to introduce
GraphQLPersistedRequestStrategy
property that takes precedence over the rc setting file.Steps to reproduce
Relevant log output
No response
Additional Context?
No response
Version
13.0.5