Provide GeneralEquipment type enumeration and guidance to user

[danyill]

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

In the GeneralEquipment editor, the type appears to be a free text string. But what should it be? What is the range of options?

Describe the solution you'd like

Could we provide a drop-down or range or a tooltip or similar to make this clearer:

IEC 61850-6 Ed 2.1, s 9.2.7.

Requirements

Users should be able to infer how to validate a field without reading the standard... The SCT should make the options clear.

Suggestions for a specific user interaction

When I click on the type field, a drop-down with the values, BAT, MOT, FAN, PMP, FIL, VLV and AXN and beneath this, somehow, to show that beginning with E and capital letters is also allowed.

Alternatively, perhaps an information icon in the top right corner with a tooltip could be used to show this (but it's less preferred because it's not as context-sensitive).

[JakobVogelsang]

This is a bit tricky. The pattern does have an enumeration for the most, but unfortunately or fortunately also E[A_Z]{3}. This is not possible to cover with a select field.

I do get your point however and would propose to give it some room in the refinement session.

[JakobVogelsang]

Add oscd component oscd-combobox.

[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]

Regrettably, lack of activity does not imply lack of need.

Still relevant and requires attention.

On Sun, 10 Sep 2023, 07:06 github-actions[bot], @.***> wrote:

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!

— Reply to this email directly, view it on GitHub https://github.com/openscd/open-scd/issues/1134#issuecomment-1712580183, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFEXX5JOQZ35ABAPN5PR4DXZS423ANCNFSM6AAAAAAT2YORQE . You are receiving this because you authored the thread.Message ID: @.***>