{"action":"created","issue":{"url":"https://api.github.com/repos/rhomobile/rhodes/issues/553","labels_url":"https://api.github.com/repos/rhomobile/rhodes/issues/553/labels{/name}","comments_url":"https://api.github.com/repos/rhomobile/rhodes/issues/553/comments","events_url":"https://api.github.com/repos/rhomobile/rhodes/issues/553/events","html_url":"https://github.com/rhomobile/rhodes/issues/553","id":63821328,"number":553,"title":"Rhom newORM does not remove {} from object IDs","user":{"login":"jtara","id":958610,"avatar_url":"https://avatars.githubusercontent.com/u/958610?v=3","gravatar_id":"","url":"https://api.github.com/users/jtara","html_url":"https://github.com/jtara","followers_url":"https://api.github.com/users/jtara/followers","following_url":"https://api.github.com/users/jtara/following{/other_user}","gists_url":"https://api.github.com/users/jtara/gists{/gist_id}","starred_url":"https://api.github.com/users/jtara/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jtara/subscriptions","organizations_url":"https://api.github.com/users/jtara/orgs","repos_url":"https://api.github.com/users/jtara/repos","events_url":"https://api.github.com/users/jtara/events{/privacy}","received_events_url":"https://api.github.com/users/jtara/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-03-23T20:14:15Z","updated_at":"2015-03-23T20:18:35Z","closed_at":null,"body":"It seems that at some point in Rhodes' evolution, Rhom started ignoring `{}` around object IDs. I'm not quite sure when that started, but it is easily demonstrated. Search for the same object ID, with or without `{}` around it. With `new_orm = 0` both will succeed. With `new_orm = 1` it will fail with the surrounding `{}`.\r\n\r\nI'm not sure what the developers' intention is. Ignoring `{}` seems a hack to work-around the fact that Rhodes `url_for()` likes to gratuitously add `{}` around object IDs in URLs. There is no good reason that I know of to do this! Maybe the thought was that this would make it easy to use JSON parsing to turn the object ID into a native type?\r\n\r\nIn any case, the `{}` are a pain to deal with. I have old code sprinkled everywhere that looks like this:\r\n\r\n``` ruby\r\n @venue = Venue.find @params['id'].to_s.gsub /[{}]/, '' \r\n```\r\n\r\nHowever, this seems no longer needed, because at some point somebody changed Rhom to just ignore the `{}`.\r\n\r\nThis hasn't been applied to newORM, though, and so it is inconsistent with oldORM.\r\n\r\nYou should decide what to do about the whole `{}` mess, and then whether or not this should still be \"fixed\" in Rhom.\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/rhomobile/rhodes/issues/comments/85175745","html_url":"https://github.com/rhomobile/rhodes/issues/553#issuecomment-85175745","issue_url":"https://api.github.com/repos/rhomobile/rhodes/issues/553","id":85175745,"user":{"login":"jtara","id":958610,"avatar_url":"https://avatars.githubusercontent.com/u/958610?v=3","gravatar_id":"","url":"https://api.github.com/users/jtara","html_url":"https://github.com/jtara","followers_url":"https://api.github.com/users/jtara/followers","following_url":"https://api.github.com/users/jtara/following{/other_user}","gists_url":"https://api.github.com/users/jtara/gists{/gist_id}","starred_url":"https://api.github.com/users/jtara/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jtara/subscriptions","organizations_url":"https://api.github.com/users/jtara/orgs","repos_url":"https://api.github.com/users/jtara/repos","events_url":"https://api.github.com/users/jtara/events{/privacy}","received_events_url":"https://api.github.com/users/jtara/received_events","type":"User","site_admin":false},"created_at":"2015-03-23T20:18:35Z","updated_at":"2015-03-23T20:18:35Z","body":"I notice that newORM IDs do not have a decimal point (or period) in them, as oldORM IDs do.\r\n\r\nThis seems a red herring, though. I can't think of a reason that this would influence a decision to include or not include `{}` around object IDs in URLs.\r\n\r\nThere's no REST \"standard\" that I know of that uses `{}`. I have no idea where this convention came from, and perhaps the URL convention should be reviewed. It would at least be informative to understand why the `{}` are even being used."}}