Skip to content
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

Cascade Dropdown return bad results #1597

Closed
ibelar opened this issue Jan 21, 2021 · 3 comments · Fixed by #1599
Closed

Cascade Dropdown return bad results #1597

ibelar opened this issue Jan 21, 2021 · 3 comments · Fixed by #1599
Assignees
Labels

Comments

@ibelar
Copy link
Contributor

ibelar commented Jan 21, 2021

Look like model condition are not set properly when using cascade dropdown since #1559

In https://ui.agiletoolkit.org/demos/form-control/dropdown-plus.php No product is shown when selecting Category and SubCategory

Screen Shot 2021-01-21 at 10 43 43 AM

@mvorisek
Copy link
Member

mvorisek commented Jan 24, 2021

@ibelar Are you sure this is really an issue and you did not selected a parent without any child item?

tested https://ui.agiletoolkit.org/demos/form-control/dropdown-plus.php with different input:

image

In https://ui.agiletoolkit.org/demos/_unit-test/lookup.php Sub category shoudl be filter by selected category but retrun all of them

was it ok before? - if so, please trace the issue, or @georgehristov might help, I did not developed this UI control

@ibelar
Copy link
Contributor Author

ibelar commented Jan 24, 2021

@mvorisek - definitely a bug - In your picture Mustard should be under Spread sub category and not Gravie.

Look like it is coming from Atk4\Data from recent changes - Seems like the model reference is not set correctly and not related to the proper selection.

@ibelar
Copy link
Contributor Author

ibelar commented Jan 25, 2021

Fix in #1599

Lookup problem previously report was ok. - no fix needed there

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging a pull request may close this issue.

3 participants