Magnolia.K

@Pand9 Is your request an option to output only the evaluated lazy vals?

In Json4s, if you use snakizeKeys, it does not judge whether the key is a number or not, so it will be converted to a uniform underscore. Since snakizeKeys is...

@folex Sorry for responding to a very old issue, is there any code that reproduces the problem listed in this issue?

@folex thanks! I reproduced the problem 3.7.0-M2, too. I will analyze it from now on.

@folex The current native parser does not meet the JSON specifications since RFC 7159. More specifically, top-level objects other than Array and Object are now allowed, but the native parser...

@xuwei-k Should we write the idea of binary compatibility (maintained in maintenance release but not in major version upgrade) in README? I think changing the code for this is nonsense.

How about reverting the above commit for 3.6.x series and committing it again for 3.7.x?

@charpov The current situation is the intended behavior. If you need to provide arguments for all existing fields, you will have less freedom in handling JSON. However, you can also...

Certainly, there are situations where you want to check that there are no extra fields in test applications. We cannot guarantee that they can be added immediately, but we will...

@0xfaded This is a comment on an old issue, but I think this is a very rare use. Isn't it appropriate to add a function to Json4s itself, such as...