Searched hist:bea7239dedd8acf3a331707c77c76579fb97cfbb (Results 1 – 4 of 4) sorted by relevance
| /plugin/struct/_test/ |
| H A D | AggregationFilterTest.php | bea7239dedd8acf3a331707c77c76579fb97cfbb Wed Jul 12 12:52:21 UTC 2023 Andreas Gohr <andi@splitbrain.org> change the way filters are rendered
Instead of a form, now links are used that immeadiately apply a selected
filter. To construct the link, the type's renderTagCloudLink() method is
reused.
Still to do:
* make it possible to apply multiple filters (this might need some
adjustments on the renderTagCloudLink() method signature)
* do ensure that one selected filter does not collapse all filter
possibilities. Cloud currently does this by implementing it's own
SearchConfig in SearchCloud, but that seems to be limited to handling
a single schema and field. I think it would make more sense to be able
enable/disable the dynamic filter handling for the standard
SearchConfig
* Improve styling. This is currently just a very quick rendering on top
of <details>
|
| /plugin/struct/syntax/ |
| H A D | filter.php | bea7239dedd8acf3a331707c77c76579fb97cfbb Wed Jul 12 12:52:21 UTC 2023 Andreas Gohr <andi@splitbrain.org> change the way filters are rendered
Instead of a form, now links are used that immeadiately apply a selected
filter. To construct the link, the type's renderTagCloudLink() method is
reused.
Still to do:
* make it possible to apply multiple filters (this might need some
adjustments on the renderTagCloudLink() method signature)
* do ensure that one selected filter does not collapse all filter
possibilities. Cloud currently does this by implementing it's own
SearchConfig in SearchCloud, but that seems to be limited to handling
a single schema and field. I think it would make more sense to be able
enable/disable the dynamic filter handling for the standard
SearchConfig
* Improve styling. This is currently just a very quick rendering on top
of <details>
|
| /plugin/struct/meta/ |
| H A D | AggregationFilter.php | bea7239dedd8acf3a331707c77c76579fb97cfbb Wed Jul 12 12:52:21 UTC 2023 Andreas Gohr <andi@splitbrain.org> change the way filters are rendered
Instead of a form, now links are used that immeadiately apply a selected
filter. To construct the link, the type's renderTagCloudLink() method is
reused.
Still to do:
* make it possible to apply multiple filters (this might need some
adjustments on the renderTagCloudLink() method signature)
* do ensure that one selected filter does not collapse all filter
possibilities. Cloud currently does this by implementing it's own
SearchConfig in SearchCloud, but that seems to be limited to handling
a single schema and field. I think it would make more sense to be able
enable/disable the dynamic filter handling for the standard
SearchConfig
* Improve styling. This is currently just a very quick rendering on top
of <details>
|
| /plugin/struct/ |
| H A D | style.less | bea7239dedd8acf3a331707c77c76579fb97cfbb Wed Jul 12 12:52:21 UTC 2023 Andreas Gohr <andi@splitbrain.org> change the way filters are rendered
Instead of a form, now links are used that immeadiately apply a selected
filter. To construct the link, the type's renderTagCloudLink() method is
reused.
Still to do:
* make it possible to apply multiple filters (this might need some
adjustments on the renderTagCloudLink() method signature)
* do ensure that one selected filter does not collapse all filter
possibilities. Cloud currently does this by implementing it's own
SearchConfig in SearchCloud, but that seems to be limited to handling
a single schema and field. I think it would make more sense to be able
enable/disable the dynamic filter handling for the standard
SearchConfig
* Improve styling. This is currently just a very quick rendering on top
of <details>
|