Not sure I got your question :( could you please provide an example? OpenJson already introduces API break(s), this one can be documented if you feel it is required
On Sat, Apr 22, 2017 at 8:40 PM, Sebastien <[email protected]> wrote: > Hi Maxim, > > Thanks for your prompt action :) > This is also needed to be backported in wicket7.x / 6.x, but... > > Yes, about the test, it's a corner case that could logically leads to a > stack overflow. But the fact is that it used to work like this before, > that's why I included it in the test... > > Question: does the object need to process toJSONString at the ctor, or > should it only copy existing properties and then call toJSONString on > toString time. > If the API does not behave like before, this will lead to a *silent* API > break in wicket 6 &7... WDYT ? > > Thanks & best regards, > Sebastien. > -- WBR Maxim aka solomax
