-
Notifications
You must be signed in to change notification settings - Fork 97
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
QueryPanel: allow automatic wildcard attachment for LIKE Comparison Filters #191
Comments
justb4
added a commit
to justb4/gxp
that referenced
this issue
Jul 22, 2013
ahocevar
added a commit
that referenced
this issue
Jul 22, 2013
fix for gxp #191 - allow automatic wildcard attachment in LIKE Filters
There appeared an issue with multiple conditions in wrapWildCards when filter.filters was undefined.
I can make a patch and PR. |
justb4
added a commit
to justb4/gxp
that referenced
this issue
May 23, 2014
…fined when wildcard wrapping
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The QueryPanel/QueryFilter allows to attach explicit wildcard symbols (*) in the attribute query condition forms (for LIKE Comparison Filters with Strings). It would be handy to have a config property like 'autoWildCardAttach' that, when set to true, automatically wraps the string values of LIKE Comparison Filters with a wildcard. Together with caseInsensitiveMatch (see #189) this will provide a more modern form interaction.
This is similar to GeoExt.form (https://github.com/geoext/geoext/blob/master/lib/GeoExt/widgets/form.js), although with QueryPanel we may not need finegrained wildcard attachment control with STARTS_WITH, ENDS_WITH, CONTAINS, though this may be added later. For now CONTAINS-mode (prepend and append the wildcard) may be sufficient.
See an example here: http://lib.heron-mc.org/heron/latest/examples/querybuilder/
(try STATE_NAME like 'al').
This affects QueryBuilder.js and FilterBuilder.js (I don't think FilterField.js). I have a patch and can issue a pull.
The text was updated successfully, but these errors were encountered: