{"action":"opened","issue":{"url":"https://api.github.com/repos/jashkenas/backbone/issues/4038","repository_url":"https://api.github.com/repos/jashkenas/backbone","labels_url":"https://api.github.com/repos/jashkenas/backbone/issues/4038/labels{/name}","comments_url":"https://api.github.com/repos/jashkenas/backbone/issues/4038/comments","events_url":"https://api.github.com/repos/jashkenas/backbone/issues/4038/events","html_url":"https://github.com/jashkenas/backbone/issues/4038","id":157676180,"number":4038,"title":"Question about model#parse","user":{"login":"JSteunou","id":2323127,"avatar_url":"https://avatars.githubusercontent.com/u/2323127?v=3","gravatar_id":"","url":"https://api.github.com/users/JSteunou","html_url":"https://github.com/JSteunou","followers_url":"https://api.github.com/users/JSteunou/followers","following_url":"https://api.github.com/users/JSteunou/following{/other_user}","gists_url":"https://api.github.com/users/JSteunou/gists{/gist_id}","starred_url":"https://api.github.com/users/JSteunou/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/JSteunou/subscriptions","organizations_url":"https://api.github.com/users/JSteunou/orgs","repos_url":"https://api.github.com/users/JSteunou/repos","events_url":"https://api.github.com/users/JSteunou/events{/privacy}","received_events_url":"https://api.github.com/users/JSteunou/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-05-31T13:48:53Z","updated_at":"2016-05-31T13:48:53Z","closed_at":null,"body":"I stumble on a case where I did not understand why my `model.set` called with `{parse: true}` did not call the `parse` method. I was very surprise to discover that `parse` must be called manually before a `model.set` whereas an option `{parse: true}` is enough for Collection.\r\n\r\nWhy Collection automatically parse *inside* the set when option `parse` is true, whereas Model does the parse *outside* the set ? Model fetch/save/constructor do call the parse method with options.parse on true, `set` is really the only method with a *weird* behaviour. Is there a good reason?\r\n"}}
{"actor":{"display_login":"JSteunou"}}