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

ErrorDefinition type does not have a "package" field #1435

Open
nmiyake opened this issue Aug 17, 2023 · 0 comments
Open

ErrorDefinition type does not have a "package" field #1435

nmiyake opened this issue Aug 17, 2023 · 0 comments

Comments

@nmiyake
Copy link
Contributor

nmiyake commented Aug 17, 2023

What happened?

The ErrorDefinition type does not have a "package" field, but error types do require a package -- currently, this means that errors always use the default-package value under the types.definitions hierarchy (and that the Conjure YAML that defines errors aren't treated as valid unless a value is specified for default-package).

What did you want to happen?

The ErrorDefinition Conjure type should have a package field that behaves analogously to all other types: if specified, its value should be used as the package for the error, and the default-package field should only be used as a fallback.

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

No branches or pull requests

1 participant