Hey.

We use a couple of base components to configure some request and session state (e.g. Session component). If we want to interrogate this state using other custom components, the dependencies must run first. This all works great if the components are added to a page in the correct order so that their respective onRuns are called sequentially.

Would it be worth thinking about basic Component ordering when viewing a page in the CMS?

Loving October, great work! :)

That's a good suggestion. Perhaps components need some sort of component dependencies option so when you add your component to your page/layout, it will automatically add the dependant components first if they aren't already added, or throw an error if the dependant components don't exist.

Leave an issue on github with your above explanation and any other relevant info.