Make textKey (default "content") configurable in XML-JSON conversion

[jnothman]

The special handling of the key "content" in XML.toString results in highly unexpected behaviour in practice. Here is a patch that allows this key to be configurable. Indeed, null is a good value for most cases, and I suggest it be made the default.

[douglascrockford]

Please see the README.

[johnjaylward]

@jnothman We finally got around to trying out more configuration for the XML parser. Please see PR #412 and let us know if it meets your needs. It was based on this PR, so it should be close. Thanks.

[jnothman]

Sorry I'm not really available to comment. I can't recall the context in which I used this project.

[johnjaylward]

Thanks anyway

[jnothman]

I suppose that's a better response, at least, than Please see the README. I still can't see in the README of that time what I was possibly meant to see there.

[johnjaylward]

Yeah, at the time the readme mentioned he was looking for a maintainer

…

On Wed, Mar 21, 2018, 22:34 Joel Nothman ***@***.***> wrote: I suppose that's a better response, at least, than Please see the README. I still can't see in the README <https://github.com/stleary/JSON-java/blob/a75a060bc81bfe980bd172e985e3dd591e6c5e9b/README> of that time what I was possibly meant to see there. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#108 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAXa1wTaxkec7-FP59ooPLSZIrnZ4ubPks5tgw28gaJpZM4C5jOV> .