You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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 thedefault-package
value under thetypes.definitions
hierarchy (and that the Conjure YAML that defines errors aren't treated as valid unless a value is specified fordefault-package
).What did you want to happen?
The
ErrorDefinition
Conjure type should have apackage
field that behaves analogously to all other types: if specified, its value should be used as the package for the error, and thedefault-package
field should only be used as a fallback.The text was updated successfully, but these errors were encountered: