How does the component handle supervision trees

[shifters67]

Very well written and interesting post!

With components how do you handle supervision trees if all the components (and hence supervision trees) are independent of each other?

I would be interested in seeing an example app (beyond trivial!) that handles genserver messages eg handle_info, terminate etc.

I look forward to see what conversation this library generates!

[pragdave]

Thank you! I'd forgotten to document this.

It was important to me that you could still write the regular genserver callbacks (and you can). I'll add an example to the readme.

In terms of supervision, I have mixed feelings. To date, I've been writing my components just using the defaults, and because each is its own (Erlang) application, this has worked out fine. However, I'm also chatting in parallel with José about strategies for state (as we currently really only have strategies for process lifecycles), and this will start to involve supervision.

What I'd really like is for you to use the library and find places where it can't do what you want. Let me know, and we can discuss whether this is something that should be added or whether you can just use regular Elixir.