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

Investigate using collection: {min}..{max} to declare fields as "required" #16

Open
ribose-jeffreylau opened this issue Jan 24, 2025 · 1 comment
Labels
enhancement New feature or request

Comments

@ribose-jeffreylau
Copy link
Contributor

Motivation

Some fields in Paneron's register are required fields, while some are optional.

LutaML modelling assumes all attributes are optional.

In order to keep compatibility with Paneron, any artifacts generated from this Gem should strive to be as close as possible to what Paneron (RegistryKit) expects.

This issue investigates the possibility of encoding such requirements to LutaML models using cardinality option (collection: {min}..{max}).

@ribose-jeffreylau
Copy link
Contributor Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant