Persisted query output directory is not ignored when building the client

Is there an existing issue for this?

• I have searched the existing issues

Product

Strawberry Shake

Describe the bug

If you have setup persisted queries and have generated a persisted query for an operation named X, changing any persisted query build parameters in the .csproj will produce the following error on a re-build:

The operation name X is not unique

Steps to reproduce

1. Have a working Strawberry Shake setup and enable persisted queries

<GraphQLRequestHash>md5</GraphQLRequestHash>
<GraphQLOutput>intermediate</GraphQLOutput>
<GraphQLPersistedQueryOutput>test</GraphQLPersistedQueryOutput>
<GraphQLPersistedQueryFormat>default</GraphQLPersistedQueryFormat>

2. Build the project and observe the build running to completion and a test directory with your persisted query files being generated
3. Change any of the parameters, for example the hash format

<GraphQLRequestHash>sha256</GraphQLRequestHash>

4. Rebuild the project and observe the described error

Relevant log output

No response

Additional Context?

Deleting all previously generated persisted query files allows to build to complete and the new settings to be applied.

Version

13.0.5

Start by reproducing the rebuild in the Strawberry Shake client project using the shown .csproj properties, especially GraphQLPersistedQueryOutput. Inspect how generated persisted query files are discovered or excluded during subsequent builds. Done means changing a build parameter and rebuilding succeeds without the duplicate operation-name error or manual deletion of the output directory.