ChilliCream / ChilliCream/graphql-platform

StrawberryShake sending custom class within extensions

Open
#5,017 2 comments 0 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 your feature request related to a problem?

IDK!

The solution you'd like

sorry to open this issue but i couldn't find a soluation anywhere
i'm still new to graphql stuff
i need to send a json request to the appsync websocket server like below
{ "id": "ab591d90-a859-40e4-a003-5682e03fddaf", "payload": { "data": { "query": "Some query", "variables": { "requestorId": "ab591d90-a859-40e4-a003-5682e03fddaf" } }, "extensions": { "authorization": { "host": "HOST", "x-api-key": "x-api-key" } } }, "type": "start" }
and what i've understand from StrawberryShake Doc/src that StrawberryShake will auto handle define needed json properties like (id,payload,data,variables,extensions(if available) and the type) and you only have to define your needed properties like query,extensions ..etc is that right?

but couldn't figuare away to define the authorization class within the extensions i know that i have to define it in the "schema.extensions.graphql" some how! but idk how to do it to look like the json above!
can you please provide some example on how to do that!
sorry for my weak english

Product

Strawberry Shake

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 with the StrawberryShake documentation and the schema.extensions.graphql file mentioned in the issue, focusing on how custom extension fields are defined. Verify whether the generated request can represent the nested extensions.authorization fields shown in the example. The payload names no implementation file or test, so completion would require a focused example or test demonstrating the resulting request shape.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
api
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.