I think it depends what you plan on doing with the statuses module. It
you'll end up having other entities attached to them then I would put an
action on either statuses or issues (indexByStatus) or whatever, OR add a
parameter to the index action, but then your action would have two functions
which breaks single responsibility principle.. there isn't really a best
way, because how you do it depends how you are going to be working with the
information you have and how you are presenting the site functionality to
the users.

On Mon, Nov 1, 2010 at 16:35, Stan McFarland <[email protected]> wrote:

> Hi all,  hoping someone can offer some advice to a Symfony newbie.
>
> I have a issues table, with an attribute 'status_id' which links to a
> status table (an issue can have a status of new, open, closed,
> etc.)    My customer wants to see a list of issues (easy - handled via
> the issue/executeIndex action) but they also want to see a list of
> issues grouped by status - in other words, a separate table of issues
> for each status type, all on one page.
>
> So I can think of several ways to do it:
>
> - add an action to the issues module called "indexByStatus" with a
> corresponding template;
> - change the index action on the status module;
> - add a new action to the status module.
>
> But what's the _right_ way?  Someone told me that it was bad practice
> to add actions - that it violated the notion of RESTful interface.
>
> Any suggestions would be greatly appreciated.  Thanks!
>
> --
> If you want to report a vulnerability issue on symfony, please send it to
> security at symfony-project.com
>
> You received this message because you are subscribed to the Google
> Groups "symfony users" group.
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]<symfony-users%[email protected]>
> For more options, visit this group at
> http://groups.google.com/group/symfony-users?hl=en
>



-- 
Alex Pilon
(613) 608-1480

-- 
If you want to report a vulnerability issue on symfony, please send it to 
security at symfony-project.com

You received this message because you are subscribed to the Google
Groups "symfony users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en

Reply via email to