-
Notifications
You must be signed in to change notification settings - Fork 15
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
Table filtering stopped working from v0.22.9 #120
Comments
@jeremiedb oops sorry about this - this was work in progress, I didn't realise it's been released. Let me check and get back to you. |
@jeremiedb Can you please try the newest 0.22.13? Should revert the filters back to the previous default. |
@jeremiedb also see an example here of server side filtering and pagination (which I recommend if you have lots of data) https://github.com/GenieFramework/StippleUI.jl/blob/master/demos/tables/app.jl |
Thanks for the follow up. Yes I can confirm that using Line 78 in 721ff97
|
In order to perform table filtering, we've been using the following up to StippleUI v0.22.8:
StipplUI v0.22.9 seems to have have introduce the autogeneration of the above
template
mechanic:StippleUI.jl/src/Tables.jl
Lines 249 to 260 in 584f88f
The changed broke the above approach to filtering since the template was now duplicated.
However, after adapting the call to the following, filtering isn't working. The page displays properly along with the seach box, but there's no reactiv filtering happening when filling the search box:
The string resulting from this v0.22.10 "broken" filtering is:
For reference, the valid string resulting from original v0.22.8 table is:
Difference in causing the issue appears to be that
:filter=\"dfilter\"
is not pushed anymore in the resulting string. Maybe this was caused by the associated work on having server side filtering? Yet I think it would be desirable to maintain support for the original Quasar client-side filtering.The text was updated successfully, but these errors were encountered: