-
Notifications
You must be signed in to change notification settings - Fork 164
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
chore: Use new property filter token editor #2564
Conversation
@@ -280,3 +292,308 @@ describe.each([false, true])('token editor, expandToViewport=%s', expandToViewpo | |||
}); | |||
}); | |||
}); | |||
|
|||
const externalProperty = { |
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.
All tests below were copied from the token-editor-grouped test file, no changes to the tests was made
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2564 +/- ##
========================================
Coverage 95.78% 95.78%
========================================
Files 741 741
Lines 20282 20270 -12
Branches 6519 6840 +321
========================================
- Hits 19427 19416 -11
+ Misses 847 798 -49
- Partials 8 56 +48 ☔ View full report in Codecov by Sentry. |
Description
Using the new token editor in property filter by default with supportsGroups=false.
A follow-up for: #2490
How has this been tested?
Review checklist
The following items are to be evaluated by the author(s) and the reviewer(s).
Correctness
CONTRIBUTING.md
.CONTRIBUTING.md
.Security
checkSafeUrl
function.Testing
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.