ChilliCream / ChilliCream/graphql-platform
HotChocolate.Fusion.CommandLine WorkingDirectory confusion
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 5.8k
- Forks
- 810
- Avg merge
- 15h 39m
- Merged PRs (30d)
- 98
Description
Product
Hot Chocolate
Is your feature request related to a problem?
Specifying a working directory with dotnet fusion compose doesn't behave as a working directory. It's more a base path for discovery of subgraph packages. It doesn't affect any other relative paths.
The solution you'd like
I think we should either rename the option to something like --subgraph-base-dir or change the behavior so that all relative paths specified are resolved to the specified working directory.
For the following command (my current cwd is /home/guest)
dotnet fusion compose -w /home/tobi -p ./gateway ...
I would expect the gateway.fgp to appear at /home/tobi/gateway.fgp, instead it appears at /home/guest/gateway.fgp, because the working directory doesn't behave like working directories in other CLIs.
What do you think?
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.
Research direction
Start with the dotnet fusion compose command and inspect how -w and relative -p paths are interpreted. Decide whether the option should be renamed to a subgraph base directory or make all relative paths resolve from the supplied working directory, then verify the example command produces the expected output location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100