ChilliCream / ChilliCream/graphql-platform

Changes to .graphqlrc.json aren't picked up

Open
#5,887 2 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

🌶️ strawberry shake
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
Product

Strawberry Shake

Describe the bug

Changing something like the namespace or the name of a client in the .graphqlrc.json file is not picked up when re-building. The code will continue to build using the old namespace in the code and errors will only arise, once you build in a "clean" environment like a CI system.

Steps to reproduce
  1. Setup a project with a working Strawberry Shake client and build it
  2. Change the namespace in the .graphqlrc.json
  3. Re-build the project
  4. Observe no errors being thrown, even though the namespace was changed.
Relevant log output

No response

Additional Context?

Manually deleting the obj and bin directories and re-building correctly picks up the changes.

Version

13.0.5

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how Strawberry Shake reads .graphqlrc.json during a normal rebuild, focusing on the namespace and client name settings and the obj/bin outputs. Reproduce the issue by changing the namespace, rebuilding without deleting obj or bin, and comparing it with a clean build. Done means configuration changes are detected and the generated client uses the new values.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, graphql
Domain
build-system
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.