Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: Add service parameter multiplicity validation when registering a service #1539

Closed
1 of 2 tasks
irisyngao opened this issue Oct 6, 2022 · 0 comments · Fixed by #1538
Closed
1 of 2 tasks
Assignees
Labels
Milestone

Comments

@irisyngao
Copy link
Contributor

irisyngao commented Oct 6, 2022

Similar requests

  • I have searched and found no existing similar requests

How are you using Studio?

Legend Studio

What problems are you trying to solve?

Add a parameter multiplicity validation when registering a service.
For MANY multiplicity, the allowed range is [0.., * ].
The accepted list for service registration is [0..1] , [1] , [0..
].

Please do it on Engine side too.

Describe the solution you would like to see implemented

The accepted parameter multiplicity list for service registration is [1, 0..*, 0..1].

Describe alternatives you have considered

No response

Documentation, Design, Adoption, Migration Strategy

No response

Contribution

  • I would like to work on this feature
@github-actions github-actions bot added the Studio Core Team Opened by a member of the Studio core team label Oct 6, 2022
@akphi akphi added this to the 8.0.0 milestone Oct 6, 2022
@irisyngao irisyngao changed the title Feature request: Add a service parameter multiplicity validation when registering a service Feature request: Add service parameter multiplicity validation when registering a service Oct 6, 2022
@akphi akphi modified the milestones: 8.0.0, 9.0.0 Oct 7, 2022
@akphi akphi modified the milestones: 9.0.0, 8.0.0 Oct 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants