{"action":"closed","issue":{"url":"https://api.github.com/repos/Prismatik/dendritic/issues/197","repository_url":"https://api.github.com/repos/Prismatik/dendritic","labels_url":"https://api.github.com/repos/Prismatik/dendritic/issues/197/labels{/name}","comments_url":"https://api.github.com/repos/Prismatik/dendritic/issues/197/comments","events_url":"https://api.github.com/repos/Prismatik/dendritic/issues/197/events","html_url":"https://github.com/Prismatik/dendritic/issues/197","id":179647053,"number":197,"title":"createdAt/updatedAt as default schema/model fields","user":{"login":"nwinch","id":1647098,"avatar_url":"https://avatars.githubusercontent.com/u/1647098?v=3","gravatar_id":"","url":"https://api.github.com/users/nwinch","html_url":"https://github.com/nwinch","followers_url":"https://api.github.com/users/nwinch/followers","following_url":"https://api.github.com/users/nwinch/following{/other_user}","gists_url":"https://api.github.com/users/nwinch/gists{/gist_id}","starred_url":"https://api.github.com/users/nwinch/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nwinch/subscriptions","organizations_url":"https://api.github.com/users/nwinch/orgs","repos_url":"https://api.github.com/users/nwinch/repos","events_url":"https://api.github.com/users/nwinch/events{/privacy}","received_events_url":"https://api.github.com/users/nwinch/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/Prismatik/dendritic/labels/discussion","name":"discussion","color":"eb6420"}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":5,"created_at":"2016-09-27T23:59:27Z","updated_at":"2016-09-28T01:31:48Z","closed_at":"2016-09-28T01:31:48Z","body":"What are everyone's thoughts about including `createdAt/updatedAt` as defaults for all models?  I wonder if it would be worthwhile to run with this as opt out, instead of opt in.  So far on Hosportal and Shortlyster we've needed these two timestamps for quite a few models.\r\n\r\nHere are some pros and cons I can see.\r\n\r\n**Pros**\r\n- It feels like standard functionality that should at least have some footprint in Dendritic core - to what degree is up for discussion.  It's always helpful information that often you need for documents.\r\n- Won't need to re-add for each project.\r\n\r\n**Cons**\r\n- It could be superfluous data for some models that don't need it.\r\n- Might be possible bloat to super small schemas/models?  Not sure if that's a huge concern."}}
{"actor":{"display_login":"MadRabbit"}}