MapGraphQL issue >= 12.17.0

Is there an existing issue for this?

• I have searched the existing issues

Product

Hot Chocolate

Describe the bug

We have been setting the GraphQL path to root for over a year and it works well on12.8.2.
This is done so that when we create Named HTTP Clients on down-stream services, that the Named HTTP connection can be utilized for both GraphQL and REST type integrations over each down-stream service within a Gateway.

This is now broken in >= 12.17.0 (possibly before) but as mentioned, it works properly in 12.8.2 at least.

This further prevents us from using Swagger and HC with root-level paths and is preventing us from migrating to 13.

Steps to reproduce

1. Steps:

2. Configure Swagger within in your program start-up using the default configuration

3. Map GraphQL servers path to root. i.e. app.MapGraphQL(path: "/");

4. Run your GraphQL server and try to run swagger. i.e. https://service/Swagger

Expected Behavior:

            Swagger UI is rendered

Actual Behavior:

            BCP UI is rendered.

Relevant log output

No response

Additional Context?

Other Notes:

If you accept the default MapGraphQL(); which resolves to path i.e. “https:/service/GraphQL”, this will return BCP rendered UI, and then when you run https://service/Swagger the Swagger UI is rendered. Unfortunately this breaks a ton services that we have already created.

Version

= 12.17.0

[jkears]

@michaelstaib … So we managed to get this to work… had to regenerate all of our services, but at least we are now finally running on 13.0.5, bring on Fusion!

Cheers

[jkears]

@michaelstaib … plus this all relates to how we resolve our gateway end-points, thus if this is changing in Fusion, then it may not be a problem in the future.