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.

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

Generic encoding with field names #39

Open
kirelagin opened this issue Mar 1, 2021 · 3 comments
Open

Generic encoding with field names #39

kirelagin opened this issue Mar 1, 2021 · 3 comments

Comments

@kirelagin
Copy link

Currently the generic encoding turns records into simple sequences of fields.

Would it make sense to change the encoding for records or provide an alternative encoding that will store records as maps, similar to what aeson does?

@iphydf
Copy link
Member

iphydf commented Nov 24, 2023

Yes, it should be an option.

@epoberezkin
Copy link

As long aeson does not become dependency :)

@iphydf
Copy link
Member

iphydf commented Jan 29, 2024

It won't. The config object can be used here to select that option. All the info is in Generic already, so it can easily be done (even without TH).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants