{"action":"closed","issue":{"url":"https://api.github.com/repos/volkanceylan/Serenity/issues/1625","repository_url":"https://api.github.com/repos/volkanceylan/Serenity","labels_url":"https://api.github.com/repos/volkanceylan/Serenity/issues/1625/labels{/name}","comments_url":"https://api.github.com/repos/volkanceylan/Serenity/issues/1625/comments","events_url":"https://api.github.com/repos/volkanceylan/Serenity/issues/1625/events","html_url":"https://github.com/volkanceylan/Serenity/issues/1625","id":195091605,"number":1625,"title":"Opening a dialog with optional information, then acting on that information during a save/delete","user":{"login":"lquantz","id":2700083,"avatar_url":"https://avatars.githubusercontent.com/u/2700083?v=3","gravatar_id":"","url":"https://api.github.com/users/lquantz","html_url":"https://github.com/lquantz","followers_url":"https://api.github.com/users/lquantz/followers","following_url":"https://api.github.com/users/lquantz/following{/other_user}","gists_url":"https://api.github.com/users/lquantz/gists{/gist_id}","starred_url":"https://api.github.com/users/lquantz/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lquantz/subscriptions","organizations_url":"https://api.github.com/users/lquantz/orgs","repos_url":"https://api.github.com/users/lquantz/repos","events_url":"https://api.github.com/users/lquantz/events{/privacy}","received_events_url":"https://api.github.com/users/lquantz/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":5,"created_at":"2016-12-12T21:32:39Z","updated_at":"2016-12-15T20:21:15Z","closed_at":"2016-12-15T20:21:15Z","body":"Is there a good way to pass information from a dialog class to the corresponding repository classes, so we can take action on them if desired?\r\n\r\nIn my case I have a dialog that I would like to pass some optional information to under some circumstances, which ideally would cause an additional step to be taken in the repository, to add/update/delete a separate entity.\r\n\r\nAs an example, assume I'm working with automobiles and have a dialog class which I added a public boolean variable to, called \"extras\", and use it like this sometimes:\r\n\r\n```\r\nvar dlg = new MyNamespace.AutomobileDialog();\r\ndlg.extras = true;\r\n```\r\n\r\nI can then open the dialog with `dlg.loadEntityAndOpenDialog(<MyNamespace.AutomobileRow>{...})`.  \r\n\r\nWhat I'd like to do is act on that 'extras' variable during a save/update/delete action, so that if the 'extras' variable is true in the `AutomobileDialog`, then in the `AutomobileRepository `class create an `AutomobileExtrasRow` entity and either update or save or delete it, depending on what's happening in the `AutomobileRow`.  To do this I need the dialog class to tell the repository class about the 'extras' variable in some way.\r\n\r\nIf there's a better way to do this kind of thing I'm open to that as well.\r\n\r\n\r\n\r\n"}}
{"actor":{"display_login":"lquantz"}}