{"comment":{"url":"https://api.github.com/repos/balderdashy/waterline/comments/20271012","html_url":"https://github.com/balderdashy/waterline/commit/ecd3e1c8f05e27a3b0c1ea4f08a73a0b4ad83c07#commitcomment-20271012","id":20271012,"user":{"login":"mikermcneil","id":618009,"avatar_url":"https://avatars.githubusercontent.com/u/618009?v=3","gravatar_id":"","url":"https://api.github.com/users/mikermcneil","html_url":"https://github.com/mikermcneil","followers_url":"https://api.github.com/users/mikermcneil/followers","following_url":"https://api.github.com/users/mikermcneil/following{/other_user}","gists_url":"https://api.github.com/users/mikermcneil/gists{/gist_id}","starred_url":"https://api.github.com/users/mikermcneil/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mikermcneil/subscriptions","organizations_url":"https://api.github.com/users/mikermcneil/orgs","repos_url":"https://api.github.com/users/mikermcneil/repos","events_url":"https://api.github.com/users/mikermcneil/events{/privacy}","received_events_url":"https://api.github.com/users/mikermcneil/received_events","type":"User","site_admin":false},"position":5,"line":61,"path":"lib/waterline/utils/ontology/is-capable-of-optimized-populate.js","commit_id":"ecd3e1c8f05e27a3b0c1ea4f08a73a0b4ad83c07","created_at":"2016-12-22T08:20:14Z","updated_at":"2016-12-22T08:20:14Z","body":"@particlebanana No model should ever support more than one datastore, so in WL schema (or wherever this is getting normalized) I think we can safely just leave this as-is as a string in the model definition, right?  It might take a bit longer to go in there and rip out that stuff, but it's well worth it to get rid of the confusion (otherwise, time will corrode our respective memories as to the intended behavior, and increasingly corrupted versions of these checks will spread like cancer every time we need to access a model's datastore-- time to nip in in the bud)"}}
{"actor":{"display_login":"mikermcneil"}}