SearchPanes and SearchBuilder do not consider pre-filtering of the table.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- csharp
- Domain
- backend-api-design
Research direction
Start with Controllers\SearchPanesController.cs and reproduce the issue at /examples/extensions/searchPanes.html using the documented site Where filter. Trace how SearchPanesOptions and SearchBuilderOptions are generated relative to the filtered table data. Done means both option sets exclude values hidden by the top-level filter, and the example no longer offers selections that return zero records.
Written by the indexing model from the issue text.
Description
When you apply a top level filter on a table, this is not taken into account by the options presented by SearchBuilderOptions or SearchPaneOptions.
Setup
Using the current example download for Editor. Showing this with SearchPanes because it is easier to see in the browser:
- Modify
Controllers\SearchPanesController.csto add a top level filter on site using the Where clause
var response = new Editor(db, "users")
.Model<UploadManyModel>()
.Where("site", "1", "=")
- Run the project and visit
/examples/extensions/searchPanes.html
Result
The resulting table shows the correct data set:
However, the SearchPanes options still show the options from the full data set:
This includes the other options like Name:
Selecting one of the pre-filtered names results in zero records found, while the options show there should be one.
Expected behavior
Pre-filtered items are hidden from the SearchPane/SearchBuilder options.
This could result in data leaking, or weird results from logically deleted records.
- Dominant language
- C#
- Stars
- 19
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from DataTables/NET
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
DataTables/NET#27 · 1 comment ·
-
Async methods? Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
DataTables/NET#25 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
DataTables/NET#24 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
DataTables/NET#18 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
DataTables/NET#17 ·
Similar issues
-
Status: Waiting triage Type: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
nanoframework/Home#1857 ·
-
kind/bug kind/regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
unoplatform/uno.toolkit.ui#1646 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nightscout/nocturne#1379 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
elastic/esql-dotnet#47 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100