Re: Using alternative encodings for specific Catalyst actions

Does anyone have any bright ideas on how to skip the Unicode::Encoding plugin's charset validation on parameters for an individual action without actually editing Unicode::Encoding itself, or is that my only option?

Looking at the source, yes, subclassing is your only option

Quickest way, override sub _handle_param_unicode_decoding to skip decoding based on some variable (say local $CatMyPlugUnicodeEncoding::DONT=1; )

The proper way requires more knowledge than I have about moose/catalyst introspection, sub prototypes , etc ... basically, where/how to configure this as a method option

Comment on Re: Using alternative encodings for specific Catalyst actions Download Code

Replies are listed 'Best First'.
Re: Using alternative encodings for specific Catalyst actions by JohannShunt (Novice) on Oct 31, 2011 at 16:51 UTC
Thanks for that - I've done as you suggested and subclassed it, and that works fine as a patch for now. Hopefully the callbacks from the 3rd party provider will get more intelligent on encodings. Would be nice if there was a neat way of being a little less strict in Catalyst itself though.	[reply]