# Admin/dashboard-next.json TypeError (no implicit conversion of Date into String)

**URL:** <https://meta.discourse.org/t/admin-dashboard-next-json-typeerror-no-implicit-conversion-of-date-into-string/90293>\
**Category:** Bug\
**Created:** [June 20, 2018, 10:53am UTC](https://meta.discourse.org/t/admin-dashboard-next-json-typeerror-no-implicit-conversion-of-date-into-string/90293 "2018-06-20T10:53:16Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![j.jaffeux](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/j.jaffeux/32/60297_2.png) [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)\
**Post date:** [June 20, 2018, 12:44pm UTC](https://meta.discourse.org/t/admin-dashboard-next-json-typeerror-no-implicit-conversion-of-date-into-string/90293/6 "2018-06-20T12:44:53Z")

</div>

@sam Before the patch the `r` variable [discourse/app/models/report.rb at main · discourse/discourse · GitHub](https://github.com/discourse/discourse/blob/master/app/models/report.rb#L290) was:  
`{"hours"=>5.8700340581401, "date"=>"2018-05-21"}`

After patch:  
`{"hours"=>5.8700340581401, "date"=>Mon, 21 May 2018}`

I fixed it with [FIX: crashes with date conversion in reports · discourse/discourse@fa43969 · GitHub](https://github.com/discourse/discourse/commit/fa43969fe246ed4a3f246b6bb01cb44053f84765) as we don’t need `Date` parsing anymore since it’s already a `Date`.

---

_[View the full topic](https://meta.discourse.org/t/admin-dashboard-next-json-typeerror-no-implicit-conversion-of-date-into-string/90293)._