ChilliCream / ChilliCream/graphql-platform
StrawberryShake tooling appears to overwrite .graphqlrc.json
@michaelstaib is already working on this.
Since Oct 30, 2022.
- Dominant language
- C#
- Stars
- 5.8k
- Forks
- 810
- Avg merge
- 15h 39m
- Merged PRs (30d)
- 98
Description
Is there an existing issue for this?
- I have searched the existing issues
Describe the bug
Issues that I discovered (In order of discovery)
- Build fails with numerous "error CS0102: The type 'blah blah blah' already contains a definition for '{propertyName}'"
- The obj\Debug\net6.0\berry\ directory contains code both the client name specified in my .graphqlrc.json file and "Client.Client.cs"
- The .graphqlrc.json file is overwritten with very sparse content (see below)
Here is the content
{
"projects": [
{
"schema": [
"bin/Debug/net6.0/schema.graphql"
],
"documents": [
"bin/Debug/net6.0/**/*.graphql"
]
}
}
After syncing versions to 13.0.0-preview.66 across client and server, and deleting files, I was able to build without issue. In retrospect, I think this may be caused by the difference in versions, particularly on the client, but it's not clear to me why that would result in changes to the .graphqlrc.json file at all.
Steps to reproduce
-
Starting State
- Blazor Client
- StrawberryShake.Tools: 13.0.0-preview.47
- StrawberryShake.Blazor: 13.0.0-preview.47:
- Server
- HotChocolate.AspNetCore: 13.0.0-preview.52
- Blazor Client
-
Build successfully
3: Update Client Tools
- Blazor Client
- StrawberryShake.Tools: 13.0.0-preview.66
- StrawberryShake.Blazor: 13.0.0-preview.47:
- Server
- HotChocolate.AspNetCore: 13.0.0-preview.52
- Build - should be unsuccessful
Relevant log output
I'm not able to provide logs due to security restrictions at my firm. Numerous instances of the following error occurred: "error CS0102: The type 'typename' already contains a definition for 'propertyName'"
Additional Context?
No response
Product
Strawberry Shake
Version
13.0.0-preview.66
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.