Skip to content

[Feature]: Merge Multiplicity Lower/Upperbound into one field #174

@spah-soptim

Description

@spah-soptim

Problem statement

Currently multiplicity fields are in two fields for lower and upper bound.

Proposed solution

They should be merged into one field for the multiplicity.
There should be a validation that checks if the format of the multiplicity is correct.

Alternatives considered

No response

Value and impact

Currently we "normalize" the multiplicity. The user should be able to specify directly how they want their multiplicity.

Suggested acceptance criteria

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request
    No fields configured for Feature.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions