Omar Marzouk

Hello! thanks for the quick response! You raise a very good point! However, we already do this for primitive data, and as it stands, this causes the tracer to print...

another related point, as it is today, the queries are also part of the trace: https://github.com/strawberry-graphql/strawberry/blob/main/strawberry/extensions/tracing/opentelemetry.py#L56 Meaning that if a user does not use query `variables` and embeds the data...

Hello! After discussion with some colleagues from the platform team at my company, they suggested that we "mask" all inputs (i.e. set them to be empty), and avoid writing the...

@patrick91 I'm really sorry I've been incredibly busy the past months, yes I would be happy to add a test for it. I will try to do it next week

@patrick91 Hi, sorry it took much more than a week 😅 I got covid and then busy at work. However, I'm up and running again, and just pushed a test....

I have also learned that nulls should not be passed in to the `set_attribute` function as its behaviour is undefined, so I have added a line to skip arguments that...

@patrick91 Hi! is this solution still relevant/ok? can we maybe move forward with it to get rid of the errors? or what do u think?

it is a `map` object similar to the `variables` field, so the input request would look something like this: ```{"query":"query getAccount($id: ID!) {\n getAccount(id: $id) {\n id\n name\n\n }\n","variables":{ "id":...

Would be nice to have it in the upcoming couple months. We would love if we can start using it early next year

@patrick91 hello! do u think there is bandwidth to prioritise the refactor you mentioned during January? if not, could we add support for the variable to the existing setup? We...