Allow different extensions to be mapped to the same block name, but different contexts #1985

Open
mojavelinux opened this Issue Jan 2, 2017 · 1 comment

Projects

None yet

1 participant

@mojavelinux
Member

Allow different block extensions to be mapped to the same block name, but different contexts (aka structural containers). This allows the same block name to apply different behavior depending on what type of content it's annotating.

Example:

[custom]
====
Custom example block.
====

[custom]
****
Custom sidebar block
****

A unique block extension should be block name + context.

This can be partially alleviated if the extension knows which type of block it's handling, which is being addressed in #1606.

@mojavelinux mojavelinux added this to the v1.6.0 milestone Jan 2, 2017
@mojavelinux mojavelinux self-assigned this Jan 2, 2017
@mojavelinux
Member

If we did this, it would allow us to set the cloaked context on the config object instead of passing it as an attribute.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment