PascalSenn
PascalSenn
@michaelstaib @monco83 @glucaci I opened a pr on the otel repo: https://github.com/open-telemetry/opentelemetry-dotnet/pull/5402#issue-2161254541
@glen-84 We did remove it once for ef core and then added it again: https://github.com/ChilliCream/graphql-platform/issues/6604#issuecomment-1810072311 So i am not sure what to do now. I believe if you do not...
This is the context: https://github.com/ChilliCream/graphql-platform/commit/28ed6ae19cf24a68e59a40409ae1aeba9c10fc90 So you only apply it when the property is nullable and ef does not complain?
Is there any chance this Pull Request can be revived?
Hi @sabuydee Thanks for reporting this issue. We have this under test, so this has to be a combination of things. Can you provide a simple repro of the issue...
@SeanTAllen, sorry, I didn't have this on my radar! @michaelstaib, this looks good to me. It's just moving the convention resolution into the branch that actually needs it.
we plan to also allow `/graphql/oauth` which would help. But the redirect urls must be on the same endpoint. otherwise BCP cannot capture it. At the moment we use the...
@onionhammer One thing that I don't quite understand is how this worked for you previously on the web. I mean, we opened up a popup for authroization, then we redirected...
@onionhammer See this >What we used to do is open BCP at localhost/graphql/, and the redirect url used to just be localhost/graphql/, which worked just fine with B2C, then at...
Can you share your csproj file