ChilliCream / ChilliCream/graphql-platform
Make it easier to define REST routes for predefined queries
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?
This is already possible but will have to do it manually: define a GET endpoint and replace args to build the query and execute.
The solution you'd like
Ideally, I'd like to define the route and use gql args to build the query.
query ($fromRoute: Int!, $fromQuery: Int) @http(get: "/api/{fromRoute}") { .. }
Arguments could come from route values or the query string.
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
The issue names no files or tests. Start by reading the existing predefined-query handling and the manual GET endpoint approach described in the report. Done means a route can be declared for a predefined query, with arguments supplied from route values or the query string and used to build and execute the query.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, graphql
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100