We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I noticed the global filters are not working. Made a quick work around to handle:
protected virtual void ProvisionGlobalSearchPayload(ref TableFilterModel tableFilterPayload, string[] props) { if (!tableFilterPayload.Filters.ContainsKey("global")) return; foreach (var prop in props) { var value = (tableFilterPayload.Filters["global"] as JObject)["value"]; var matchMode = (tableFilterPayload.Filters["global"] as JObject)["matchMode"]; if (tableFilterPayload.Filters.ContainsKey(prop)) { tableFilterPayload.Filters[prop] = new JArray { new JObject { ["value"] = value, ["matchMode"] = matchMode, ["operator"] = "or" }}; } else { tableFilterPayload.Filters.Add(prop, new JObject { ["value"] = value, ["matchMode"] = matchMode, ["operator"] = "or" }); } } tableFilterPayload.Filters.Remove("global"); }
Forces you to define global filters on serverside but seems to work nice :)
Might be able to use this to work it into the library...
The text was updated successfully, but these errors were encountered:
Hi rileybwesley
Thank you for your solution. Your solution make me inspire for implement global filter for this library.
Sorry, something went wrong.
No problem :)
No branches or pull requests
I noticed the global filters are not working. Made a quick work around to handle:
Forces you to define global filters on serverside but seems to work nice :)
Might be able to use this to work it into the library...
The text was updated successfully, but these errors were encountered: