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
fix: use the default query on adding a new tab #3441
base: main
Are you sure you want to change the base?
Conversation
🦋 Changeset detectedLatest commit: 00aba1d The changes in this PR will be included in the next version bump. This PR includes changesets to release 4 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
makes sense to me. do any other @graphql/graphiql-maintainers have feelings about this? |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #3441 +/- ##
==========================================
+ Coverage 55.31% 55.81% +0.49%
==========================================
Files 115 114 -1
Lines 5351 5305 -46
Branches 1451 1443 -8
==========================================
+ Hits 2960 2961 +1
+ Misses 1965 1912 -53
- Partials 426 432 +6
|
I'm for this change 👍 |
two things:
|
@cimdalli so it seems this clashes a bit with previously expected behavior: when so we need to revert this for headers and do the same for query/defaultQuery. otherwise, it's a change in functionality and requires a new minor version CC @dimaMachina who added tests for this expectation, what do you think? |
When a new tab is added, it sets the query value as an empty string instead of
defaultQuery
value. Tab default query value should bedefaultQuery
variable if it's set on the component. Otherwise, it should be DEFAULT_QUERY constant.