ChilliCream / ChilliCream/graphql-platform
Allow tag directive on filter and sort types
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?
I'm using v15.1.12 and I need to be able to tag any type including filter and sort types (and fields). I need to be able to set tags in order to exclude them from the fusion composition process. Looks like I can manually set tags via .Directive(new HotChocolate.Types.Tagnew HotChocolate.Types.Tag("my-custom-tag")) however this doesn't match the normal convention of either using the descriptor extension or attribute.
The solution you'd like
Adding tags is possible on everything through descriptor extension or attribute. Preferrable this is also added to v15 as I don't think we can immediately port some of our code to v16 (and it's not released/stable yet).
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
No files or tests are named. Start by locating the existing tag descriptor extension and attribute APIs, then compare how filter and sort types and fields are defined; done means tags can be applied through the normal descriptor or attribute convention and are honored during Fusion composition exclusion, including the requested v15 compatibility.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, graphql
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100