Timeline for Are "open-closed principle" and "less coupling" rationales to use global state?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 27, 2019 at 19:21 | comment | added | StackOverthrow | @candied_orange Indeed. As your link says, it depends on how closely related the parameters are. The asker's UserData class may already be guilty of being a bag of random junk, since token sounds like something transient while name sounds like a property of the user. | |
| Nov 27, 2019 at 19:13 | comment | added | candied_orange | @NoU up to a point. See Introduce Parameter Object | |
| Nov 27, 2019 at 19:08 | comment | added | StackOverthrow | Or to take it a step further, that constructor should take token, name, and balance rather than getting them from userData. | |
| Nov 27, 2019 at 16:45 | history | edited | candied_orange | CC BY-SA 4.0 | edited body |
| Nov 27, 2019 at 16:43 | comment | added | Winston Ewert | It seems to me that the whole point of the example was that information from the login process needs to be used in the About dialog. Storing the data locally on the LoginPage makes that not work at all. | |
| Nov 27, 2019 at 15:32 | history | edited | candied_orange | CC BY-SA 4.0 | added 806 characters in body |
| Nov 27, 2019 at 15:21 | history | answered | candied_orange | CC BY-SA 4.0 |