Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • 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. Commented Nov 27, 2019 at 16:43
  • Or to take it a step further, that constructor should take token, name, and balance rather than getting them from userData. Commented Nov 27, 2019 at 19:08
  • @NoU up to a point. See Introduce Parameter Object Commented Nov 27, 2019 at 19:13
  • @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. Commented Nov 27, 2019 at 19:21