Respect Validation 2.2版本无setParam函数时的消息翻译实现方案咨询

Hey there! I’ve worked extensively with Respect Validation across versions, so I can help you adjust your translation setup for v2.2.x. The error handling API changed significantly from v1.1, so let’s walk through the updated approach step by step.

Key Changes to Note #

In v2.x, Respect Validation dropped the setParam method on exceptions and instead integrates translation directly with rules (either globally or per-rule) using a Translator component. This makes the translation flow more consistent and flexible.

Option 1: Global Translator Setup (Recommended) #

The simplest way is to set a global translator that all rules will use automatically. This avoids repeating translation setup for every field:

use Respect\Validation\Validator;

// Assume $translator is your pre-configured translation instance
// (e.g., Symfony's Translator, or a custom implementation of Respect's Translator interface)
Validator::setDefaultTranslator($translator);

Then update your validation loop:

foreach ($rules as $field => $rule) {
    try {
        $localeField = $translator->trans($field);
        // Set the translated field name and run validation
        $rule->setName($localeField)->assert($request->getParam($field));
    } catch (\Respect\Validation\Exceptions\NestedValidationException $e) {
        // getMessages() now returns automatically translated messages
        $this->errors[$field] = $e->getMessages();
    }
}

Option 2: Per-Rule Translator Setup #

If you need to use different translators for specific rules (instead of a global one), you can attach the translator directly to each rule instance:

foreach ($rules as $field => $rule) {
    try {
        $localeField = $translator->trans($field);
        // Attach translator and translated field name to the rule
        $rule->setTranslator($translator)->setName($localeField)->assert($request->getParam($field));
    } catch (\Respect\Validation\Exceptions\NestedValidationException $e) {
        $this->errors[$field] = $e->getMessages();
    }
}

Custom Translation Logic #

If you need to add custom processing to your translated messages (e.g., special formatting for certain fields), use getRawMessages() to fetch untranslated raw messages, then process them manually:

catch (\Respect\Validation\Exceptions\NestedValidationException $e) {
    $translatedMessages = array_map(function ($rawMessage) use ($translator) {
        // Add your custom translation logic here if needed
        return $translator->trans($rawMessage);
    }, $e->getRawMessages());
    
    $this->errors[$field] = $translatedMessages;
}

Important Note: Translation Key Format #

Make sure your translation files use the v2.x key format! Respect Validation v2.x switched from single curly braces {name} to double curly braces {{name}} for placeholders. For example:

• v1.x: "The {name} field is required"
• v2.x: "The {{name}} field is required"

内容的提问来源于stack exchange，提问作者Miky