Timeline for Is it appropriate to process a property in the setter?
Current License: CC BY-SA 3.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 21, 2019 at 6:39 | answer | added | Kain0_0 | timeline score: 2 | |
| Mar 21, 2019 at 2:50 | answer | added | John Wu | timeline score: 0 | |
| Nov 5, 2017 at 19:30 | review | Close votes | |||
| Nov 10, 2017 at 3:03 | |||||
| Nov 2, 2017 at 21:58 | history | tweeted | twitter.com/StackSoftEng/status/926206938840535041 | ||
| Oct 27, 2017 at 16:59 | answer | added | JacquesB | timeline score: 8 | |
| Oct 27, 2017 at 16:58 | answer | added | Jon Raynor | timeline score: 1 | |
| Oct 27, 2017 at 15:58 | answer | added | TheCatWhisperer | timeline score: 5 | |
| Oct 27, 2017 at 15:20 | comment | added | Nathan | Hang on, if you set it to null you ignore that and keep the old field values? | |
| Oct 27, 2017 at 14:08 | comment | added | CodesInChaos | Name = Name; having a significant effect is dubious. Why don't you add a public RawName property and assign to it? | |
| Oct 27, 2017 at 14:05 | review | Close votes | |||
| Nov 3, 2017 at 3:12 | |||||
| Oct 27, 2017 at 13:59 | answer | added | paparazzo | timeline score: 0 | |
| Oct 27, 2017 at 13:50 | comment | added | gnat | Possible duplicate of Is it considered a bad practice to add logic in a property setter? | |
| Oct 27, 2017 at 13:46 | history | asked | Maxime | CC BY-SA 3.0 |