Timeline for Providing context in Class name, even though the namespace provides context
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 15, 2017 at 10:04 | audit | Suggested edits | |||
| May 15, 2017 at 10:05 | |||||
| May 6, 2017 at 8:07 | answer | added | Ewan | timeline score: 1 | |
| May 5, 2017 at 7:17 | comment | added | amon | Will the namespace context be visible in code that uses these classes? E.g. do you expect to always see MySolution.Event.Registration.BeginRequest, or would users import that class name and write BeginRequest? In my experience, it's usually the latter – thus indicating that each class name should provide enough context in isolation. | |
| May 4, 2017 at 21:07 | comment | added | Machado | Related reading: .Net Framework Naming Guidelines. | |
| May 4, 2017 at 21:04 | review | Close votes | |||
| May 19, 2017 at 3:01 | |||||
| May 4, 2017 at 20:54 | history | edited | Devin Gleason Lambert | CC BY-SA 3.0 | added 265 characters in body |
| May 4, 2017 at 20:46 | history | asked | Devin Gleason Lambert | CC BY-SA 3.0 |