Skip to content

i18n our errors #8

Description

@stevan

We discussed this, the errors put into the document can either be a string, or then can be a HASH ref with a single key "code" which contains a string which can be fed into an i18n mechanism (Locale::Maketext, etc) and properly i18n these errors using some kind of plugin.

Or, we could do it totally different.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions