- 🇬🇧United Kingdom catch
This all changed in the meantime, we have policy exceptions for entities with base classes, the 1-1 rule for one-class interfaces etc.
Per #2661926: [policy no-patch] Document that interfaces without an @api tag can have API additions during a minor release → we now have a reason to tag interfaces as @api to differentiate them from those that aren't.
There are definitely interfaces in core that we'd treat as @api, so we should start tagging them.
Most of the discussion in the original issue was around the Entity API, so I'd suggest we start with that, then use it as a template to open issues for other subsystems.
Once we've tagged something @api there's no going back (at least once it's in a tagged release), so important to take it a step at a time.
Closed: outdated
11.0 🔥
entity system
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
This all changed in the meantime, we have policy exceptions for entities with base classes, the 1-1 rule for one-class interfaces etc.