Support quoting of filtered-list search strings

[danyill]

Is your feature request related to a problem? Please describe.

As a user of OpenSCD I want to be able to filter based on the user interface that appears to me. If there is a space in an identity string or a collection of "paths" then that shouldn't prevent me from carrying out my query.

For instance, there is a space in the identity string of an LGOS LN, e.g. "LGOS 7" and I want to search all subscriptions for this.

Similarly if I am looking for the protection trip instance 1 operate value, which we might show in OpenSCD as "PTRC 1.Op" then I should be able to do a "fully-qualified" search for this.

Describe the solution you'd like

For the examples above I would like to type in either:

• 'LGOS 7'
• "LGOS 7"
• "PTRC 1.Op"
• Be able to filter on e.g. ExtRef descriptions with spaces in them

And expect the filter to behave correctly.

Requirements

Allow quotes (either single or double quotes).

Suggestions for a specific user interaction

User enters string in filtered text entry field.

[danyill]

We decided we would like more sophisticated behaviour, possibly with regex search, and possibly with chips and the ability to manipulate them in some fashion.

We agreed that we need to decide on what the more sophisticated behaviour would be (and perhaps create a new issue/discussion). What I heard was:

• consistency across filtering/search interfaces
• ability to provide regex search
• a less opaque understanding of what is searched and predictable output

[github-actions[bot]]

Hello there,

Thank you for opening this issue! We appreciate your interest in our project. However, it seems that this issue hasn't had any activity for a while. To ensure that our issue tracker remains organized and efficient, we occasionally review and address stale issues.

If you believe this issue is still relevant and requires attention, please provide any additional context, updates, or details that might help us understand the problem better. Feel free to continue the conversation here.

If the issue is no longer relevant, you can simply close it. If you're uncertain, you can always reopen it later.

Remember, our project thrives on community contributions, and your input matters. We're here to collaborate and improve. Thank you for being part of this journey!

[danyill]

Still relevant and requires attention.