Yann Simon

What about https://github.com/kamilkisiela/graphql-hive/issues/2449 Is it similar to https://github.com/kamilkisiela/graphql-hive/issues/254 ?

Thanks for the explanation, it makes perfect sense. And I guess that `Operation::is_introspection` returns true for all kinds of introspection, schema and type name? I'm using this information to know...

I don't know exactly what I should check? Do you have something in mind? Are you asking me because of my [role with GraphQL](https://commercetools.atlassian.net/wiki/spaces/TL/pages/661061968/What+does+Yann+do)?

Maybe you should ask [priceless team](https://commercetools.atlassian.net/wiki/spaces/PT/pages/81745925/CoCo+Groups+and+Teams#Priceless-Team) then?

I'm not sure if this example is more "useful|. I'm using https://lib.rs/crates/vss and it's quite clear how to use it ``` #[tokio::main] async fn main() { axum::serve(tcp, app) .with_graceful_shutdown(shutdown_signal()) .await...

@tobx indeed, having fields served from both URLs is strange. Would you like to open a PR to fix this behavior?

I've made one PoC so that we can better imagine how the API would be: https://github.com/tokio-rs/axum/pull/3000 @bengsparks could you also make one for the approach you're suggesting. It seems very...

I personal like having to change the usage site. I guess it would be very easy to have a function taking a `Scheme` and forgetting about the risks of using...

My only fear is about: - one developer does a change to use a spoofable value. - later another developer is using this value without knowing that it can be...

I have the feeling that the community consensus is tending towards `Spoofable` wrapper. To make progress, let's go for this. It's always a step in more security awareness.