David Buchmann

so basically this would mean to evaluate embedded twig in the content, but evaluate it in a sandbox rather than the full application context? is that already done somewhere? it...

for the question at hand, i think we want a specific thing that uses extra logic to figure out where to link to. in the sandbox, we could define a...

we need to find a better name. `content_on_method` would suggest that you add different content based on the request method. but what you want to do, if i get it...

i would not do any magic. if people want magic method names, they hopefully use FOSRestBundle which does that nicely. i would simply add that mapper, and allow explicit configuration...

i would make the configuration something like ``` yaml controller_by_class: My\Class: - methods: [put, post] controller: service:method - controller: service:readMethod Other\Class: service:method ``` so if the value of Other\Class is...

the rest bundle is just my argument why we should not try to do a lot of automatic model + method to controller action mapping ;-)

i have no complete overview of what FOSRest can do, but afaik its a lot about annotations. there is quite some doc in the symfony docs: http://symfony.com/doc/current/bundles/FOSRestBundle/index.html i am not...

you can also use base classes or interfaces to group things. would your idea be to have something like this? ``` - controller: controller.deleteAction methods: [DELETE] classes: - AppBundle\Document\Article -...

> each document should have a > dedicated HTTP entry point imo (e.g. a BlogPost::createAction() > shouldn't be able to created Pages imo). note that this will never work for...

do you have a WIP pull request that i can use as a starting point and try to fix?