Declarative Controller/Handler - Githubissues

0xgeert / Canonical

Chorio - Datalayer as a service

0 stars 0 forks source link

Declarative Controller/Handler #7

Open 0xgeert opened 11 years ago

0xgeert commented 11 years ago

Is there really custom-controlled code needed? can't all things be done declaratively that you'd normally want done in a controller?

Especially when we get application-workflow done declaratively (or using sagas which transfers the flow to the domain-model), in addition to all the operations on single domain-models we have covered pretty much everything?

per-route:

defaults (middleware)
validation (middleware)
authentication (middleware)
authorization (middleware)
from payload to repo (translation)
from repo to view (translation). I.e: view-model

0xgeert commented 11 years ago

For declarative Controller thoughts on Sails see: https://github.com/balderdashy/sails/issues/176

Some things as part of model OR resource (api DTO) -declaration:

prevent fields from returning using GET (e.g: password and hash) -> RESOURCE
defaultsTo some specific value -> MODEL
calculatedFields such as slug -> MODEL OR RESOURCE?
- MODEL if we want to bake-in the calculation (and only update on changes to other fields the calculation depends on)
- RESOURCE if we want to calculate on the fly on each return