contextual communication between components

[AndyOGo]

After I quickly fixed #26 (publish/subscribe) I see the possible use case of a list of child components who need to communicate between each other within a specific context.

<axa-context>
  <axa-foo></axa-foo>
  <axa-bar></axa-bar>
</axa-context>

<axa-context>
  <axa-foo></axa-foo>
  <axa-bar></axa-bar>
</axa-context>

With a small hack this can be archived currently using incremental channels, like:

let n = 0;
publish(`channel-${n}/change`, ...)
subscribe(`channel-${n}/change`, ...)

...
++n;
publish(`channel-${n}/change`, ...)
subscribe(`channel-${n}/change`, ...)

Requirements

• enable intercommunication between hierarchy-agnostic components
• opt-in to select kind of context
• pass contextual data down

[AndyOGo]

A concrete use case is showing/hiding the mobile main navigation upon burger button click.

[AndyOGo]

@LucaMele
Well, seems that the constructor of a parent Web Components is called after the connectedCallback of child components, which breaks context retrieval...

Possible that this is related to how Web Components are bootstrapped #27 or our DOMContentLoaded fix...

[LucaMele]

regarding ur last comment: Thank you, but as said in the #41 it follows the proposed standard and therefore no issue.

[LucaMele]

regarding ur last comment: Thank you, but as already said it follows the proposed standard and therefore no issue.

[AndyOGo]

Okay, I got your point.
Nevertheless we currently face this problem and this makes it a bug.
I'm fine if you want to call it feature, but it needs to be handled for the sake of this project.

[LucaMele]

Agreed, as an enhancement and with the title as finding a valid solution to a problem and not complaining the specs. Lets sit together and find a solution

[LucaMele]

closing as new plib version is live. If issue is with v2 still relevant, please re-open