Timeline for Exposing warnings\errors from data objects (that are also list returned)
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 21, 2012 at 13:08 | vote | accept | Oren Schwartz | ||
| Apr 18, 2012 at 16:38 | comment | added | Evan Plaice | @OrenSchwartz "others retrieve a list of them (thus disables throwing exceptions)," Why? What's wrong with sub-classing the list class with a custom implementation and wrapping the iterable property with exception handling logic, it's actually pretty easy to do. You could also implement a new exception interface to that all of the base data types inherit to guarantee commonality. If it's throwing an exception, expose an exception. | |
| Apr 18, 2012 at 16:26 | history | edited | gnat | CC BY-SA 3.0 |
spelling and personal stuff cleanup
|
| Mar 19, 2012 at 15:47 | answer | added | om471987 | timeline score: 1 | |
| Dec 18, 2011 at 9:43 | comment | added | Oren Schwartz | thought about having an IFieldErrorWrapper that'll encapsulate each field, and will expose its events. the UI will then decide how to handle them. | |
| Dec 18, 2011 at 8:43 | comment | added | NoChance | Just wondering, how would events propagate across layers? | |
| Dec 18, 2011 at 7:31 | history | edited | Oren Schwartz | CC BY-SA 3.0 |
added 89 characters in body
|
| Dec 18, 2011 at 5:44 | comment | added | DKnight | You did a good job framing a problem, but you might want to rewrite the end a little to ask a specific question. Right now there's not a question in there at all :-) | |
| Dec 18, 2011 at 3:53 | history | asked | Oren Schwartz | CC BY-SA 3.0 |