Should we deprecate the `skipUrlEncoding` option in core-client?
MaryGao opened this issue · comments
In core-client-rest we have skipUrlEncoding
option at the very beginning because we can't customize the skipEncoding information for parameter. But now in RLC we have allowReserved
option for path parameter and for Modular we have already fully supported url template and no longer need to customize the value of skipUrlEncoding
. Should we deprecate the skipUrlEncoding option in core-client?
Maybe we could mark this option at @deprecated
and then collect any feedbacks, if there is no objections for long term it would be a signal for us to remove this.
/cc @qiaozha