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

serde support #1

Open
ibotty opened this issue Apr 3, 2024 · 3 comments
Open

serde support #1

ibotty opened this issue Apr 3, 2024 · 3 comments

Comments

@ibotty
Copy link

ibotty commented Apr 3, 2024

Is serde support in scope (as a feature flag) or should it be in a separate repository?
@Ethiraric
Copy link
Contributor

It is planned and will be in a different repository. There is no need of pulling the Yaml object (which is what this crate is about) in order to implement serde support.

@jgrund
Copy link

jgrund commented Jul 23, 2024

Hi, is there a pointer to a repo where this will (eventually) live?

@gnattishness gnattishness mentioned this issue Aug 15, 2024
Open
@not-my-profile not-my-profile mentioned this issue Sep 18, 2024
Merged
Ethiraric added a commit that referenced this issue Oct 2, 2024
@Ethiraric
Add support for nested implicit flow mappings.
750c992 
These are corner cases not tested by the `yaml-test-suite`.
Parsing for the reported input has been fixed, as well as other
similar-looking inputs which make use of nested implicit flow mappings
and implicit null keys and values.

Fixes #1.
@masnagam masnagam mentioned this issue Oct 4, 2024
Open
@Caellian
Copy link

There is no need of pulling the Yaml object (which is what this crate is about) in order to implement serde support.

Would be nice to have those types re-exported though. There's cases where being able to manipulate yaml objects before passing them to serde greatly simplifies implementation:

  • inferring enum variant based on present map keys (i.e. manual #[serde(untagged)] deserialization),
  • partially destructuring yaml data without complicated all-encompassing structs,
  • etc.

@StayBlue StayBlue mentioned this issue Jan 5, 2025
Open
@GrabbenD GrabbenD mentioned this issue Feb 2, 2025
Open
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
@ibotty @jgrund @Ethiraric @Caellian