Skip to content

Docs: Create ADR for default content versioning #112

Open
@brian-smith-tcril

Description

@brian-smith-tcril

We need a way to communicate notable changes to the default content of a slot. This should cover changes that aren't breaking changes to the API of a slot (no changes to plugin props or location on page), so plugins would still work, but any plugins that rely on the default content might need to be tweaked to account for the default content changes.

A good example of this comes from openedx/frontend-app-learning#1713 where slots are moving from having something as default content to having nothing. Any plugins that replace the default content entirely will continue to work without any changes, but any plugins designed around wrapping the default content would instead be wrapping nothing.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions