Bonus, the code that dumps the route map can also dump the parameters templates. This could be used for unit testing.
*routes map
Thanks in advance XD
Obviously, that's over simplified. But I've just audited an app that checks the same parameter 4 times while routing a request object through 3 helpers and then punts the request back with a 403. For a small app, that's not a big deal, but for an app handling 100K+ requests per second, intuitively that seems like a waste of resources and cloud billable time.
I don't want to tell anyone else how to build their framework, but I'd second that the above is, in principle, a very good idea. See for example how .Net MVC applications often have a request object and response object from endpoints. My job is security testing, and I can tell you definitively that forcing input to conform to a schema, in that case by safely deserialising it to a well-defined type, takes a significant axe to certain types of security issues.
You could do this, for example, by using a type with some annotations along the lines of "take this from the body, this from parameter X, etc", and populating an instance of that type before the endpoint is even called.
Of course, you can already do that with the JSON body at least.
.Net calls these "Data Transfer Objects"
Will be happy to accept PR's as well
@ptman:kapsi.fi tracking it here, I just went through the steps of creating a new app and got the same error revel/revel#1528
and I run revel in docker as well
or the revel based app, to be more accurate
not ideal
and prod env it's ideal to statically compile and run it
docker can autostart
systemd can autostart
supervisord is an option
use whichever you find easiest
thanks
would be great to finally get this added
The fix was to add a dependency to the missing module in the
init.go file like
import (
"github.com/revel/revel"
_ "github.com/revel/modules"
)
New revel project doesn't want to run on account of a module reference to github.com/myesui/uuid which doesn't exist
Make a build