Skip to content

Schema: required attribute might be unnecessary #162

@ashfame

Description

@ashfame

When we save a subject while defining its blueprint, we save it completely empty (just its sourceUrl). So not only enforcing "required" attribute would be a problem, but it's unnecessary? Why do we need it? Is there an issue with the behavior of operating with whatever data we have as is?

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions