Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add GraphQL UI to test endpoints in OIDC Dev UI #20140

Merged
merged 1 commit into from
Sep 15, 2021
Merged

Add GraphQL UI to test endpoints in OIDC Dev UI #20140

merged 1 commit into from
Sep 15, 2021

Conversation

phillip-kruger
Copy link
Member

Same as for Swagger UI, this allows you to navigate from OIDC Dev UI in the logged in state to the GraphQL UI to test your endpoint (if you have graphql endpoints)

graphql_oidc_devui

Signed-off-by:Phillip Kruger phillip.kruger@gmail.com

@sberyozkin
Copy link
Member

Hi @phillip-kruger This is a cool enhancement, only a minor update is proposed.

I also have a question - in #20092 GraphQL the authenticated subscription is not working - how does it work in this case ?

@phillip-kruger
Copy link
Member Author

Yea, not sure about WebSockets and if this will work.

Signed-off-by: Phillip Kruger <phillip.kruger@gmail.com>
@phillip-kruger phillip-kruger added the triage/waiting-for-ci Ready to merge when CI successfully finishes label Sep 14, 2021
@quarkus-bot
Copy link

quarkus-bot bot commented Sep 14, 2021

Failing Jobs - Building 5e993ab

Status Name Step Failures Logs Raw logs
✔️ JVM Tests - JDK 11
JVM Tests - JDK 11 Windows Build Failures Logs Raw logs
✔️ JVM Tests - JDK 16

Full information is available in the Build summary check run.

Failures

⚙️ JVM Tests - JDK 11 Windows #

- Failing: extensions/amazon-lambda/deployment 
! Skipped: docs extensions/amazon-lambda-http/deployment extensions/amazon-lambda-rest/deployment and 6 more

📦 extensions/amazon-lambda/deployment

io.quarkus.amazon.lambda.deployment.testing.LambdaDevServicesContinuousTestingTestCase.testLambda line 41 - More details - Source on GitHub

org.opentest4j.AssertionFailedError: expected: <0> but was: <1>
	at org.junit.jupiter.api.AssertionUtils.fail(AssertionUtils.java:55)
	at org.junit.jupiter.api.AssertionUtils.failNotEqual(AssertionUtils.java:62)

@phillip-kruger phillip-kruger merged commit 550e59a into quarkusio:main Sep 15, 2021
@quarkus-bot quarkus-bot bot added this to the 2.3 - main milestone Sep 15, 2021
@quarkus-bot quarkus-bot bot removed the triage/waiting-for-ci Ready to merge when CI successfully finishes label Sep 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants