Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #27487: restore import/export buttons when EditAll uses conditional policies #27488
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
base: main
Are you sure you want to change the base?
Fixes #27487: restore import/export buttons when EditAll uses conditional policies #27488
Changes from all commits
9568e07649b42dc2decc3815f0b7f8e6c55c2d09a6e04f2ed4e87aceb83d8b3f55ba06d8b83798396c03792920eFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Quality: Mutable shared test state not reset between tests
The new
describeblock mutates module-levelmockGlossaryTermPermissionandmockContext(lines 330-336, 358-365) without resetting them afterward. While this matches the existing pattern in the file, the new tests depend on and further propagate leaked state. For example, the first new test (line 327) inheritsmockContext.typefrom whatever the previous test set it to (line 233 sets it toGLOSSARY_TERM), then overrides it toGLOSSARYat line 335 — which then leaks into the second new test.Currently this doesn't cause failures because test execution order is deterministic and these are the last tests, but it's fragile. Adding a
beforeEachorafterEachin the newdescribeblock to snapshot and restore the shared objects would make these tests order-independent.Suggested fix:
Was this helpful? React with 👍 / 👎 | Reply
gitar fixto apply this suggestionUh oh!
There was an error while loading. Please reload this page.