allow routes to operate on location hash

[kingsleyh]

At the moment I can't run Kemal and server the API and the Mint app from the same kemal instance. This means I have to run 2 servers and I can't make use of Kemals session handling and I have to enable cors.

Because the routes are in the url the Kemal server picks them up instead of the Mint app - In Elm it uses location hash for routing. Could we do the same thing - and optionally choose to use location hash as I think this would solve my issues running inside the same server.

[kingsleyh]

I've found a workaround in Kemal which seems to work ok

  error 404 do |context|
    context.response.content_type = "text/html"
    context.response.status_code = 200
    File.read(File.join("public", "index.html"))
  end

it feels a bit wrong to use the error stuff though - it would be better if a custom handler or a middleware could do it instead

[gdotdesign]

Would it be okay if this would be supported?

routes {
  /path# {
  }

  /path#:entity/:page (entity : String, page : String) {
  }
}

Edit: It's added in master ➡️ 9211065

[kingsleyh]

I think kemal would still pick up the /path part first but I'm not sure - If it's in master I could try and see if it works

[gdotdesign]

Should be fixed in 0.4.0 @kingsleyh can you validate it? Should I close this issue?

[kingsleyh]

yup all good :)