StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PONeed help fitting a design flow into REST
primarykey
Id
11165007
data
AcceptedAnswerId
11165548
AnswerCount
2
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-06-22T22:34:43.690
FavoriteCount
0
LastActivityDate
2012-07-26T03:16:26.287
LastEditDate
2012-07-26T03:16:26.287
LastEditorUserId
698590
OwnerUserId
1148811
ParentId
0
PostTypeId
1
Score
0
ViewCount
64
LastEditorDisplayName
text
Body
I'm having a bit of a trouble understanding how to fit a particular design flow I have into a proper REST architecture. Let me explain the flow: I'm creating technical support website where users can submit ProblemRequests. On the front page, the user selects all the categories he's having trouble with and clicks "get help," which then redirects him to the next page where he fills out some forms to submit his request. Here are the pages: <a href="http://i.minus.com/ijzMDj1LiPxFI.png" rel="nofollow">Page 1 - Select Problem Categories</a> <a href="http://i.minus.com/ibzdee6NK8hqhV.png" rel="nofollow">Page 2 - Fill out Problem Request</a> Page 2 basically acts like the NEW action for a ProblemRequest. The thing is each ProblemRequest depends on multiple ProblemCategories, so a nested route isn't going to work here. The next thing that comes to mind is sending in all relevant ProblemCategories ids as an GET param for the NEW ProblemRequest action, but I would rather not expose the IDs in the URL. A Multi-Part form sort of comes to mind, but that involves making ProblemRequests have state, where some would be complete and others incomplete. I don't want to deal with the implications, because in reality this is a one page submission, not a very long-winded process. What would work ideally is to override the NEW action for the ProblemRequests controller to respond to POST operations, but I don't know if this is considered bad programming practice. Is this a cardinal sin? Is it okay for me to change the NEW action to respond to POST instead of GET? Please advise, Thanks in advance.
Tags
<ruby-on-rails-3><rest><routing>
Title
Need help fitting a design flow into REST
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USGaffi
UserOwnerUserId
1. USroflmao
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.