SearchPanes and SearchBuilder do not consider pre-filtering of the table.

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:

1. Modify Controllers\SearchPanesController.cs to add a top level filter on site using the Where clause

var response = new Editor(db, "users")
    .Model<UploadManyModel>()
    .Where("site", "1", "=")

2. 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.

Inizia da Controllers\SearchPanesController.cs e riproduci il problema in /examples/extensions/searchPanes.html usando il filtro Where documentato del sito. Traccia come vengono generate SearchPanesOptions e SearchBuilderOptions rispetto ai dati filtrati della tabella. Il lavoro è completato quando entrambi gli insiemi di opzioni escludono i valori nascosti dal filtro di primo livello e l’esempio non offre più selezioni che restituiscono zero record.