On Wed, Nov 12, 2025 at 10:56 AM Fujii Masao <[email protected]> wrote:
> On Wed, Nov 12, 2025 at 10:10 AM Masahiko Sawada <[email protected]> > wrote: > > +1 for hard-coding the supported encoding list. I think it's a good > > start point. We can revisit the idea of dynamically constructing the > > encoding list if we're concerned about its maintenance cost. > > +1 > > Regards, > > -- > Fujii Masao > Thanks everyone for reviewing my proposal. I've hard-coded the valid list of encoding names. Also, I modified the hint string into like "Valid encodings are \"hex\", \"base64\", \"base64url\", and \"escape\"." by adding "and" before "escape". I attached my v2 patch to this message. Please let me know freely if you have any additional questions. Regards,
v2-0001-Added-error-hints-for-invalid-binary-encoding-names-.patch
Description: Binary data
