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

Toolbox: When a limit exists on a previous tab's query, a new tab will enter the previous tab's query again #9

Open
mjfwebb opened this issue Nov 8, 2023 · 2 comments

Comments

@mjfwebb
Copy link
Contributor

mjfwebb commented Nov 8, 2023

Describe the bug

When a limit exists on a previous tab's query, a new tab will enter the previous tab's query again

Type definitions
Some simple type definitions:

type Movie {
  title: String!
  actors: [Person!]! @relationship(type: "ACTED_IN", direction: IN)
}

type Person {
  name: String
  movies: [Movie!]!
}

To Reproduce
Steps to reproduce the behavior:

  1. In GraphQL Toolbox build a schema and go to the query tab
  2. Enter a query which includes a limit option, like this:
query MyQuery {
  movies(options: {limit: 10}) {
    title
  }
}
  1. Add a new tab with the + button, it will look normal and empty
  2. Start entering text (more than one character, to go beyond the initial intellisense) into the blank query input
  3. You'll now see the previous tab's query again and you'll be editing the limit option

Expected behavior
Nothing from the previous tab should be carried over.

Screenshots

image

@neo4j-team-graphql
Copy link
Contributor

Many thanks for raising this bug report @mjfwebb. 🐛 We will now attempt to reproduce the bug based on the steps you have provided.

Please ensure that you've provided the necessary information for a minimal reproduction, including but not limited to:

  • Type definitions
  • Resolvers
  • Query and/or Mutation (or multiple) needed to reproduce

If you have a support agreement with Neo4j, please link this GitHub issue to a new or existing Zendesk ticket.

Thanks again! 🙏

@neo4j-team-graphql
Copy link
Contributor

We've been able to confirm this bug using the steps to reproduce that you provided - many thanks @mjfwebb! 🙏 We will now prioritise the bug and address it appropriately.

@mjfwebb mjfwebb transferred this issue from neo4j/graphql Mar 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants