Timeline for Passing a selectlist to the view based on database models from viewmodel is a MVC anti-pattern
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 23, 2017 at 16:30 | history | edited | Jamal | CC BY-SA 3.0 |
deleted 48 characters in body; edited title
|
| Feb 17, 2013 at 8:21 | vote | accept | annemartijn | ||
| Feb 17, 2013 at 1:38 | answer | added | Tesserex | timeline score: 5 | |
| Feb 14, 2013 at 19:15 | history | tweeted | twitter.com/#!/StackCodeReview/status/302133962409668609 | ||
| Feb 14, 2013 at 16:58 | comment | added | Jeff Vanzella |
Why do you need to pass the SelectList? Can't you have the items for the select list in one Property, and the selected value in another?
|
|
| Feb 14, 2013 at 16:40 | history | migrated | from stackoverflow.com (revisions) | ||
| Feb 14, 2013 at 13:20 | comment | added | annemartijn | In my opnion this is an anti-pattern, because I have a context in the model layer and contexts are bound to controllers. | |
| Feb 14, 2013 at 10:06 | comment | added | undefined | I personally don't think its an anti-pattern at all, the model is exclusively for the view so inclusion of view constructs is IMO not a bad thing | |
| Feb 14, 2013 at 9:34 | comment | added | Jeroen | In such cases i'm adding my selectlist to my model and pass it to my view, but stil wondering if there is a better solution + | |
| Feb 14, 2013 at 9:30 | history | asked | annemartijn | CC BY-SA 3.0 |