Daniel
@tomasgarzon @goinnn instead of going the fork route, could someone else be given permissions to merge? Django 3.2 goes EOL in the spring, it would be really nice to get...
looking forward to having this in 2.0 :+1:
@domchristie any comments on getting this merged?
It would clean up the code, but we often use humps on custom objects (decamelize our JavaScript models for a snake_case API). I think `_isPlainObject` would break that behavior.
You have some great points. After looking into it more with @bitwurx , this pull request (and the other type checking already in the library) is really a work around...
I think this is the current pseudo-code for `_processKeys` ``` Is the given item a special type? (Boolean, int, Date, regex, file) return the special type un-modified Is the given...
I've been thinking about this more: - Object mutation is scary - Backwards compatibility might not be maintained - Doesn't fix circular references: I've got a special object, in my...
Yes, as a configuration. Each conversation method has its own strengths and weaknesses. The only way to support all object types is to support different conversion stratagies. It would be...