[GitHub] [superset] shubham1811 commented on issue #24511: Dependent Filter Issue :- If the parent Filter value is changed then the dependent filter with previous selected value is not getting removed if its not in the dependent filter data(options)

["shubham1811 (via GitHub)" <gi...@apache.org>]

shubham1811 commented on issue #24511:
URL: https://github.com/apache/superset/issues/24511#issuecomment-1697819185

   > Having the same issue here in 2.1.0
   > 
   > I can add that :
   > 
   > * if you have 'Select first filter value by default ' active on the filters and click on the 'CLEAR ALL' button while parent filter is loading, you'll get 'null' as a selected value in child filters
   > * if you have 'Select first filter value by default ' active on the filters and then click on the 'CLEAR ALL' button while parent and child filters are set, it will reset the parent filter but not the children. another 'CLEAR ALL' will then clear the children.
   > 
   > It feels like any change in the parent should cascade in the child filter, and child filters should be loaded only when the parent filter has finished loading.
   
   Yes Correct child filters should be loaded only when the parent filter has finished loading.


-- 
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