Document relation to server side routing about kee-frame HOT 4 CLOSED

Hi! Thanks for posting back :)

You are right, documentation about how to coordinate routing on server and client is absent. I want kee-frame to be a complete solution for getting quickly up and running, so this needs some work.

I like your solution with cljc, I guess you need something like that if you want to be more specific about when to bypass server routing and forward it to the client.

The intention of the sample project is not to ignore the URI. The way I normally do it is to match server urls first, and fall back to index.html on anything that is not found. This is of course not optimal as routes that should normally be 404 will render as index.html. But a fair trade off for simple apps. You can still use a 404 handler in the client, if the route is still not found there.

Another technique is to use things like /api and /client, so anything under /client matches as index.html on the server.

I don't really know if people actually settled on any "best practice" for this, so not sure what to recommend. But definitely need to include it in the README!

from kee-frame.

Let's keep this open, I would like to be reminded to document this.

from kee-frame.

Falling back to index.html and customising the 404 page in the javascript is a perfectly good solution. And since the server requires no knowledge of the UI routes is simpler too. If guidance was provided in the README I would favour this approach over mine, with perhaps a mention of how alternate static pages might be served, and reference to something like the code example above.

Prepending UI routes with /client would also work, but at the expense of making it visible to the customer-facing URLs.

from kee-frame.

FWIW I found a bug with my postwalk implementation: bidi's route params also match the keyword? predicate. I've switched to the implementation where :index is matched if none of the server routes match, and the cljs code displays the 'not found' page.

from kee-frame.