Add menu node in context path menu to select ancestor data

Issue #24 wontfix
Christian Oeing repo owner created an issue

Any plan to have a editor interface when you want to add a custom path, that would look contextholder up hierarchy. Instead of struggling with #1.xxx, #2.xxx, #3.xxx

This doesn't only depend on the Context for which the path is selected but also on the parent context this context is a child of.

Comments (6)

  1. Christian Oeing reporter

    The CollectionObserver (introduced with 1.0.9) will be a cleaner way to connect a parent context with its child contexts. The # syntax should be either deprecated or reworked to work with the drop down instead of the custom path.

  2. Christian Oeing reporter

    It shouldn't be necessary to access a parent context from a child context as contexts should be self contained. There are many possibilties (events, CollectionObserver,..) to create a cleaner connection.

  3. Log in to comment