Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

More compatibility with aeson #5

Open
5 tasks
paf31 opened this issue Nov 18, 2015 · 5 comments
Open
5 tasks

More compatibility with aeson #5

paf31 opened this issue Nov 18, 2015 · 5 comments

Comments

@paf31
Copy link
Owner

paf31 commented Nov 18, 2015

  • Date types
  • Different SumEncodings
  • Maps
  • Tuples
  • Either

etc.
@bsermons bsermons mentioned this issue Jul 7, 2016
Open
@swamp-agr
Copy link

Hello Phil,

I was worried about absence of such Decode/Encode instances for DateTime, Date, Time and similar types. I am a newcomer in Purescript world. Could you please suggest the way how to implement these instances?

Best Regards,
Andrey

@paf31
Copy link
Owner Author

paf31 commented Jun 12, 2017

You would need to define instances for newtype wrappers.

@swamp-agr
Copy link

Phil,

Thanks a lot for fast response.
I will implement in this way in order to avoid Orphans.

Best Regards,
Andrey.

@zyla zyla mentioned this issue May 18, 2018
Closed
@shmish111
Copy link

I've just created #52 to allow compatibility with Aeson records, see PR for more detailed explanation.

@csicar csicar mentioned this issue Sep 5, 2020
Open
@ongyiren1994
Copy link

Is there a plan to add option UntaggedValue to SumEncoding ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@paf31 @shmish111 @swamp-agr @ongyiren1994