{"action":"created","issue":{"url":"https://api.github.com/repos/erikras/redux-form/issues/1226","repository_url":"https://api.github.com/repos/erikras/redux-form","labels_url":"https://api.github.com/repos/erikras/redux-form/issues/1226/labels{/name}","comments_url":"https://api.github.com/repos/erikras/redux-form/issues/1226/comments","events_url":"https://api.github.com/repos/erikras/redux-form/issues/1226/events","html_url":"https://github.com/erikras/redux-form/issues/1226","id":162500370,"number":1226,"title":"[v6] FieldArray Radio Example","user":{"login":"tyrsius","id":1187432,"avatar_url":"https://avatars1.githubusercontent.com/u/1187432?v=4","gravatar_id":"","url":"https://api.github.com/users/tyrsius","html_url":"https://github.com/tyrsius","followers_url":"https://api.github.com/users/tyrsius/followers","following_url":"https://api.github.com/users/tyrsius/following{/other_user}","gists_url":"https://api.github.com/users/tyrsius/gists{/gist_id}","starred_url":"https://api.github.com/users/tyrsius/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tyrsius/subscriptions","organizations_url":"https://api.github.com/users/tyrsius/orgs","repos_url":"https://api.github.com/users/tyrsius/repos","events_url":"https://api.github.com/users/tyrsius/events{/privacy}","received_events_url":"https://api.github.com/users/tyrsius/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":27,"created_at":"2016-06-27T17:03:22Z","updated_at":"2017-08-01T00:35:11Z","closed_at":"2017-07-31T20:16:57Z","body":"I've looked at these [two](https://github.com/erikras/redux-form/issues/124) [issues](https://github.com/erikras/redux-form/issues/33), but they are either for v5 or they do not actually have a working example.\n\nRight now the behavior of radio buttons is either strange or broken. The UI updates the way it should, but the value in `onSubmit` is `on` for every field that was ever checked as a radio button. I don't see a way to tell in the form submission event to tell which item in `FieldArray` had its radio button checked.\n"},"comment":{"url":"https://api.github.com/repos/erikras/redux-form/issues/comments/319234592","html_url":"https://github.com/erikras/redux-form/issues/1226#issuecomment-319234592","issue_url":"https://api.github.com/repos/erikras/redux-form/issues/1226","id":319234592,"user":{"login":"danielrob","id":5865302,"avatar_url":"https://avatars2.githubusercontent.com/u/5865302?v=4","gravatar_id":"","url":"https://api.github.com/users/danielrob","html_url":"https://github.com/danielrob","followers_url":"https://api.github.com/users/danielrob/followers","following_url":"https://api.github.com/users/danielrob/following{/other_user}","gists_url":"https://api.github.com/users/danielrob/gists{/gist_id}","starred_url":"https://api.github.com/users/danielrob/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/danielrob/subscriptions","organizations_url":"https://api.github.com/users/danielrob/orgs","repos_url":"https://api.github.com/users/danielrob/repos","events_url":"https://api.github.com/users/danielrob/events{/privacy}","received_events_url":"https://api.github.com/users/danielrob/received_events","type":"User","site_admin":false},"created_at":"2017-08-01T00:35:11Z","updated_at":"2017-08-01T00:35:11Z","body":"@grovesNL I 100% agree with you, though I think what you're discussing is a far wider concern than this specific issue. I said some words along the lines of my personal summary of why we're at where we're at with this on another ticket (partially derived from your links above): \r\n\r\n```\r\nPerformance is actually (one of) the main reason(s) in my understanding that the Field* components mostly keep to themselves by default, and then the library provides extra selectors for the cases where the developer explicitly needs the payoff of a small performance loss that allows them to fetch the information they want. \r\n```\r\n\r\nIn saying that, I totally agree that 'the developer explicitly needing the payoff' is not an uncommon occurrence, and the tracker has a number of tickets to the effect of asking for help with this. I think we need some proposals in this regard. Aiming for an API design that is both useful and general could lead to some fun times :). "}}
{"actor":{"display_login":"danielrob"}}