Create mark categories for marked classes

The README.md for the schema already discusses how content nodes identify their accepted content with marker interfaces (See CaptionContent and so on in the Content restrictions section. I can’t link to it directly because of how Bitbucket renders markdown files.) Currently, marked nodes are sometimes using a general category like TextMark, but in other cases are using concrete mark types like Link. This will make it impossible to introduce new mark types to those nodes later without an API-breaking change.

The fix is to introduce marker interfaces for the marks a node can accept just as there already are for the types of content that they can accept.

In particular, I know that there is current work to introduce a new border mark for media nodes, and Media can’t add support for that as long as it implements Marked<Media, Link>.

Comments (3)