On Thu, Mar 6, 2014 at 1:24 AM, sri <[email protected]> wrote: > What should be done about conflicting types? e.g. dwg is >> application/x-acad, image/x-dwg, and image/vnd.dwg >> > > Just like "xml". > > https://github.com/kraih/mojo/blob/master/lib/Mojolicious/Types.pm#L30 >
Thanks, sri! I'll do that! Because alternatives are only used for detection, do all valid options need to be ordered in anyway? That is, is it necessary that application/xml be listed before text/xml? I trust then that everything else is OK with the plugin? Oh, I didn't consider... What happens when you register a type that's already registered? That is, core registers xml and certainly the plugin does too. Is it important to skip already registered types, or, because it's running only on MIME::Types, it's just going to redefine it to the same thing so it doesn't matter that it redefines what what defined in core? -- You received this message because you are subscribed to the Google Groups "Mojolicious" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/mojolicious. For more options, visit https://groups.google.com/groups/opt_out.
