future-plans: custom saved search views with JS expressions
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -148,6 +148,20 @@ This would allow:
|
||||
- Unit conversion on query (e.g. `temp > 200K` matching a stored `-73°C`)
|
||||
- Catching unit mismatches at entry time
|
||||
|
||||
## Search & views
|
||||
|
||||
### Custom search views
|
||||
Saved searches defined as JS expressions (similar to the template system), evaluated
|
||||
against each component to produce a filtered and optionally transformed list. Example
|
||||
use cases:
|
||||
- "all components with a non-empty `todo` field"
|
||||
- "all SMD resistors with no datasheet attached"
|
||||
- "all components missing a `package` field"
|
||||
|
||||
Views would be named, saved, and accessible from the nav or a dedicated views
|
||||
section. The expression receives the full component object and returns truthy to
|
||||
include it. Could later be extended to also control sort order and displayed columns.
|
||||
|
||||
## PDF / files
|
||||
|
||||
### Auto-select file after upload in file picker
|
||||
|
||||
Reference in New Issue
Block a user