Yes that would work for me, other opinions?
Jacques
Le 13/10/2015 03:31, Jacopo Cappellato a écrit :
Hi Jacques, Deepak,
we could add the method that Deepak is proposing, for backward
compatibility, with a deprecation warning and plan for removing it before
we create our next release branch.
Hi Jacques,
I think we fixed all these ContentWrapper* code in trunk code base, but it
will affect lot of custom code as well.
So IMO we have to maintain backward compatibility as well.
Can we add an get method that will use the default encoding as html?
As we generally used ContentWrapper to
Hi Deepak,
Thanks for the interest. I had exactly the same idea initially. There are indeed 600+
"'html" cases vs 80+ "url" ones.
But then I thought that some people will maybe not notice the difference and will always use the shorten version (the "html" one). Because it's about
security
Hi Jacques, Deepak,
we could add the method that Deepak is proposing, for backward
compatibility, with a deprecation warning and plan for removing it before
we create our next release branch.
Jacopo
On Mon, Oct 12, 2015 at 11:50 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:
> Hi
