> On 10 Nov 2025, at 10:06, Chao Li <[email protected]> wrote: >> On Nov 8, 2025, at 14:25, Sugamoto Shinya <[email protected]> wrote:
>> This patch adds an error hint listing the valid encoding names, >> so users can immediately see the supported options. +1. > I think hardcoding the encoding list is fragile. AFAIK, “base64url” was newly > added just a couple of months ago. > > The list is defined in encode.c (search for enclist in the file), I guess we > can add a function to return a string with a encoding names. New encodings are added very infrequently, we can revisit this if that changes but till then I think the simplicity of a hardcoded string is preferrable. -- Daniel Gustafsson
