OK, take this scenario:
app.com -> app.com/messages
/ and then routes to
/messages - this all happens on the client. No problem, initial route is loaded by server, client side routing takes control after that.
app.com/messages -> app.com
/messages and then routes to
/. Now we have our first problem - messages was rendered by the server. This is where I’m lost - there is nothing about your code or in the meteor docs that says how to route to
/messages from the server - and certainly nothing about using a different container component for that route based on what
The next layer of my question is
/messages has to show reactive data as the messages come in. If the initial container component is what provides the initial data, once the DOM is hydrated the client side stuff will take over. That data needs to be reactive though, and meteor requires
withTracker to make it reactive.
So… that means the container component has to be wrapped with
withTracker which basically is breaking routing.
I am super appreciative of your time and help here, it’s informing a big business decision right now over what to use for our next application.