{"push_id":2502749191,"size":1,"distinct_size":1,"ref":"refs/heads/date-object","head":"081c595d0e10769ddf6e983f4490d8c4a3eba852","before":"8af33ccf0ab3fc84b255d079cd5184a10495413d","commits":[{"sha":"081c595d0e10769ddf6e983f4490d8c4a3eba852","author":{"name":"Shawn Erquhart","email":"443646d156d0e0db4e143fd54251ca15b42bcccb@erquh.art"},"message":"return date object from date/datetime widgets if no format set\n\nBREAKING CHANGE\n\nAs of 1.0, the documented behavior for the date and datetime widgets was\nto always return a string value, but they were instead returning a date\nobject if the default date was not manually changed by the user. This\nwas addressed in #1143, but it became clear afterward that static site\ngenerators were depending on the raw date objects that Netlify CMS was\nunintentionally producing. Remaining as is or addressing the bug were\nboth \"breaking\" states, so this commit reverts to producing raw date\nobjects when no format is explicitly set.\n\nIt is now considered an edge case to require string dates, as most\nstatic site generators expect to parse a raw date against formatting in\na site's templates.\n\nAlso note that this commit improves the original behavior by always\nproviding a date object when no format is provided, even if the user\nmanually changes the value.","distinct":true,"url":"https://api.github.com/repos/netlify/netlify-cms/commits/081c595d0e10769ddf6e983f4490d8c4a3eba852"}]}
{"actor":{"display_login":"erquhart"}}