Imagine we have such routing in our application:
@resource 'article', ->
@route 'show', {path: '/:article_id'}
@route 'add'
And I provide view with name App.ArticleShowView, that is being resolved by convention and becomes ‘article.show’ route’s active view: i can put some logic there, and I can refer this view in my route’s template as ‘view’.
But when I change @route 'show' to @resource 'show' (resource !) and declare App.ArticleShowIndexView, I expect to get the behaviour as in previous example: this view would be routes’s ‘article.show’ active view. And it doesn’t work. Can someone please comment, is it ok at all to do such things? Is it a nice practice and why case with resource doesn’t work? Regards.