James

This is perhaps unfortunate naming, but a change of field name in serialization would be a breaking change as the fields as-is may be depended upon downstream or a older...

I'm in agreement that the naming is unfortunate, but I don't agree it is supplying incorrect information. The field data returned is correct. If I was a consumer, I wouldn't...

@dtolnay If docs are holding this back, I can make a PR for documenting this in https://github.com/serde-rs/serde-rs.github.io/blob/master/_src/container-attrs.md

Looking for comments on #2161 which is an alternative solution that is more generic over the problem

Now that I think about it, perhaps `alias_with`/`alias_all_with` could be a better name inline with `deserialize_with` and `alias` which is a loose idea of what this functionality actually provides. ```rust...

@dtolnay Any thoughts on the initial implementation or comments?

Nope, this is with master. I only discovered it while I was working on refactoring the tests in that PR. Note that PR can be merged. The solution with the...

After sleeping on the idea, my personal opinion is that the method of generating global IDs should be overridable. Node IDs don't have a specification in terms of how you...

Thinking about implementation, I'm torn on where to place the configuration. Ideally this should be a per schema option and not to the degree where you have to reference the...

My line of thinking was similar to @jparise's in respect to mix config. If the developer wished to configure on a per environment basis they could themselves with `get_env/3`. An...