Skip to content

DateTime deserialization handling #61

@Prinsn

Description

@Prinsn

I'm currently trying to use Newtonsoft JSON converters to intercept incoming data to ensure UTC for DateTime, as this gets lost on DB commit.

Currently, I can get WriteJson to be called as expected for DateTime, but not ReadJson where I expect to intercept it, so I at least know it's loaded but not sure how to handle this.

Trying to figure out if there's a standard way or feature that Breeze conducts serialization that is causing the read to never happen when deserializing objects, or if there's otherwise a way to ensure that the time gets serialized to UTC.

While this can be approached from the front end to try to pre-convert, I'm trying to just handle the problem rather than requiring the client be required to create correctly formatted data (because various frameworks are not doing it and having to figure them all out is just more of what I'm doing here)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions