You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by GitBox <gi...@apache.org> on 2022/01/10 18:51:17 UTC

[GitHub] [superset] jess-dillard commented on pull request #17976: feat(Select): [cosmetic] support allowTopOptions for select component

jess-dillard commented on pull request #17976:
URL: https://github.com/apache/superset/pull/17976#issuecomment-1009241321


   @stephenLYZ I agree with @michael-s-molina and @geido that we should keep the pattern consistent throughout the application. Michael's pagination use case makes sense as a reason to keep the current behavior (selected values appear first in the dropdown list). @stephenLYZ, I am curious what use cases you have in mind to support why this might not be the best behavior.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org