Alexander

there is a better workaround: just provide a default of None

nice idea. But maybe a proposal: why not extending graphene-protector? This extension works for strawberry as well as graphene as well as plain graphql-python And it is tested

(side note: a project of mine)

I see your point. Assigning arguments with costs is a cool idea. But how would an extension like mine retrieve the costs? It would be nice to have a function/property...

some parts I did already, for example you can exclude some path parts from adding complexity/depth. By default connections are reduced to one. Some parts which are missing, are: -...

actually it is already implemented (graphene-protector) (except I don't check the arguments yet, bug). What I need is someone who can help me with a graphql parser in rust (see...

The issue is in graphql-core (which is the python port of the reference implementation and probably also in use by adriane). https://github.com/graphql-python/graphql-core/issues/216 Of course it would be possible to build...

you can access the costs. You aren't required to block. You can even dynamically provide the limit.

Someone picked this up and build a rust parser for embedding? where do I find the rust parser? How can I test it? Or did I misunderstand?

nice, thank you