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: fetch all owners for dashboard and chart listview filters and properties modal #9784
Conversation
Codecov Report
@@ Coverage Diff @@
## master #9784 +/- ##
==========================================
+ Coverage 70.79% 70.91% +0.12%
==========================================
Files 587 183 -404
Lines 30435 17826 -12609
Branches 3152 0 -3152
==========================================
- Hits 21545 12641 -8904
+ Misses 8776 5185 -3591
+ Partials 114 0 -114
Continue to review full report at Codecov.
|
4f84c97
to
b0828c9
Compare
This most likely will conflict with #9628 |
It's not ready for merge yet. Just a heads up how they might interfere with each other. Here are the related changes: d2050b5 Feel free to merge your changes first if you are ready. |
2f68649
to
d77bb4f
Compare
Codecov Report
@@ Coverage Diff @@
## master #9784 +/- ##
=======================================
Coverage 71.35% 71.36%
=======================================
Files 585 585
Lines 30917 30932 +15
Branches 3246 3252 +6
=======================================
+ Hits 22061 22074 +13
Misses 8747 8747
- Partials 109 111 +2
Continue to review full report at Codecov.
|
be8efb7
to
1565405
Compare
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.
LGTM
…nd properties modal (apache#9784)" This reverts commit d187d28.
SUMMARY
Superset api limits records to 20 by default. @bkyryliuk recently opened a PR(#9667) to fix some of the owners dropdowns so that all records are returned by the api. The pr received some push back since changing the defaults probably isn't the best approach. This PR requests all records for the owners endpoints to fix the issue flagged in #9667.
Originally we intended to add pagination (via infinite scroll) and backend filtering. While trying to implement that approach I hit some limitations in react-select's async mode that caused me to reimplement fetching using react-select in non async mode, code is here: 90f7f79
Also since there is currently an upgrade for react-select in progress (#9628) I opted for holding off on adding more complexity until the upgrade is complete. React select is fairly fast at searching and I don't think we should expect the owners list to be that large, so I'm not convinced that adding pagination will result in a more performant end user experience than fetching all records after mount and searching locally.
TEST PLAN
ADDITIONAL INFORMATION
REVIEWERS