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

GraphQL query detail view doesn't display default information properly. #2269

Closed
bile0026 opened this issue Aug 22, 2022 · 1 comment · Fixed by #2285
Closed

GraphQL query detail view doesn't display default information properly. #2269

bile0026 opened this issue Aug 22, 2022 · 1 comment · Fixed by #2285
Assignees
Labels
type: bug Something isn't working as expected

Comments

@bile0026
Copy link
Contributor

Environment

  • Python version: 3.8
  • Nautobot version: 1.4.0 (e4112c63d4f6)

Steps to Reproduce

  1. Open a GraphQL query object

Expected Behavior

Page by default should display the "GraphQL" tab with the query details.
image

Observed Behavior

Page looks blank with the tabs along the top. Have to click one of the tabs to get information to show.
image

@bryanculver bryanculver added the type: bug Something isn't working as expected label Aug 22, 2022
@glennmatthews
Copy link
Contributor

Thanks for the report. I can confirm this bug.

@glennmatthews glennmatthews changed the title GraphQL page doesn't display default information properly. GraphQL query detail view doesn't display default information properly. Aug 22, 2022
@glennmatthews glennmatthews self-assigned this Aug 22, 2022
glennmatthews added a commit that referenced this issue Aug 25, 2022
* Fix #2269: include block.super in javascript blocks

* Fix template rendering logic so main tab is visible at render time
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 24, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type: bug Something isn't working as expected
Projects
No open projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants