Custom key decoding strategy performance about zippyjson HOT 3 CLOSED

I use .convertFromSnakeCase and a custom date formatter for my api. Most APIs I've interacted with use snake case and that's not the swift convention. (Using Codable means your object's elements have to have the same names as the JSON keys).

Just so I understand, currently ZippyJSON would fallback to apple's decoder in my use case?

from zippyjson.

.convertFromSnakeCase will not force the use of Apple's decoder. For your case, it will use ZippyJSON's, and the decoding will be about 10x faster overall. If it didn't, you would see a warning message in Xcode's console. Custom date formatters are fine, just not custom key decoding strategies. Although since you mentioned it, I'm curious, what's the dateFormat for your formatter? Could you use the .iso8601 date formatting option? It makes date parsing 10x faster.

from zippyjson.

There has not been many people requesting this, so closing for now. In the future we can explore it again. I could also be convinced to have an optional function pointer like void convertKey(char *string, int length), that converts the key in-place, probably in C

from zippyjson.