routing

Following REST it is advisable that API is discoverable and should be interlinked. Does ServiceStack support any kind of reverse routing? I'm looking for something like Url.RouteLink in ASP MVC. There's some mixed concepts stated here. In and effort of trying to comply with REST you wish to embed URI's in your responses. How best to achieve embedding URI's in your responses. You've assumed a "Reverse Routing" mechanism is how this should be done. REST style vs Strong-typing I want to be explicitly mention here that one doesn't imply the other. On the one hand you're looking to follow a REST

I am building an Express app and having some issues with routing. My '/' route is working perfectly, however other routes are not. I've looked into other questions people have posted and these have not resolved my issues. I have a routes/index.js file: module.exports = function(app){ app.use('/', require('./routes/home')); app.use('/about', require('./routes/about')); } My routes/home.js: - WORKING! const express = require('express'); const router = express.Router(); router.get('/', function(req, res) { res.render('app/home'); }); module.exports = router; My routes/about.js: - NOT WORKING!

I'm sure this will become clear as I dig in deeper, but for now it's not obvious how to make this happen. I was following the info on this helpful SO article about routing but there is an important piece missing from the example, i.e. how do you get the 'home' view to render right away without having to click the 'home' link? I've started digging into the docs to try to make sense of this, but meanwhile it seems like a useful question to have answered for posterity. I've been playing with the working jsfiddle example from the above question here and comparing with this other example I found