Should Types.ToTypeScriptType convert DateTime and DateTimeOffset to Date or string? about ntypewriter HOT 2 CLOSED

Typewriter converts them to Date thus it will stay that way in NTypewriter too as default. But I see no reason why not to make it configurable as it was done in PR #7 with nullable types.

from ntypewriter.

Last night as I was comparing all the Urls created by NTypewriter to those created by Typewriter, I realized that I was wrong to request this "feature". I still believe that best practice is to pass dates between the front end and back end as strings and not DateTime/DateTimeOffset objects. But I remembered that you can't just "fix" it on the Typescript side, you have to make your DTO use string for those fields. My suggestion for best practice date handling is to never have your DTO include a DateTime or DateTimeOffset object, but instead use strings for those fields. This puts the proper handling of the conversion to and from the Date objects in your code's control, not hidden in some middleware.

I have closed the PR and I am closing this. If someone feels this is necessary, then the PR is still there and can be modified to suit, but I don't feel this is necessary. Sorry for the noise.

from ntypewriter.