add displayabled values support

[overtrue]

some times we need custom displayable values, especially when using multi-byte encoded text scenes. for example:

HTML:

<label>banner type</label>
<select name="content_type" >
    <option value="1" data-type="image">Image</option>
    <option value="3" data-type="video">video</option>
    <option value="4" data-type="web">Web</option>
</select>
...
<div>
    <label>banner image</label>
    <input type="url" name="image" value="" placeholder="the url of banner image.">
</div>
<div>
    <label>banner video</label>
    <input type="url" name="video" value="" placeholder="the url of banner video.">
</div>
...

Rule:

    ...
    $rules = array(
              'content_type' => 'required|in:1,3,4',
              'image'        => 'required_if:content_type,1',
              'video'        => 'required_if:content_type,3',
             ),
    ...

app/lang/en/validation.php:

    ...
    'attributes' => array(
                     'content_type' => 'banner type',
                     'image'        => 'banner image url',
                     'video'        => 'banner video url',
                    ),
    ...

Request:

array(
 'content_type' => 1,
 'image'        => '',
);

Errors:

The banner image url field is required when content type is 1.

Difficult for users to understand what the number 1 is

We expect that this:

The banner image url field is required when banner type is Image.

Now we can add the values ​field to the app/lang/en/validation.php to achieve it：

    ...
    'values' => array(
                 'content_type' => array(
                                    '1' => 'Image',
                                    '3' => 'Video',
                                    '4' => 'Web'
                                   ),
                ),
    ...

Thanks!

[vandas]

thanks It is what I want

[ghost]

I also met this demand, thanks

[qufo]

That is great. the error message will be simple and easier to read.

[botherbox]

Nice work!

[iarchean]

Great work. Helped me a lot.

[crny]

能说中文不？

[overtrue]

可以用中文，不过作者可能看不懂啊，英文才是通用语言

[overtrue]

@iarchean @Alexskywin @qufo @vandas Thanks!

[jasonlewis]

I'd just usually have my option values set to "web", " image", etc.
On 4 Apr 2014 16:19, "Joy" notifications@github.com wrote:

@iarchean https://github.com/iarchean Thanks!

Reply to this email directly or view it on GitHubhttps://github.com//pull/4037#issuecomment-39532703
.

[overtrue]

@jasonlewis yes! However, the use of multi-byte encoding characters such as China or Japan, it is not convenient.

[yinmingming]

good job

[taylorotwell]

I would suggest just extend the Validator to do what you want. You can easily do so using the Validate::resolver method.

[overtrue]

ok,Thanks

[taylorotwell]

Want to re-open this to consider it further.

[overtrue]

@taylorotwell Thanks, in fact, in a non-English speaking countries is still a lot of demand.

[overtrue]

@taylorotwell Thanks!

[jinchun]

Admiration arises despite my incomprehension of what you said!

[piotr-cz]

There's no method to set $customValues like there is to set $customAttributes (unless one extends Validator class):

Custom attributes may be set either in constructor or using setAttributeNames(array $attributes).
I think this cool functionality deserves similar API.

To explain: I'm not using the default key validation.values because my models attributes overlap.

[yopop666]

May anyone help me to translate value from required_if validation rule?
More details in issue 19725

Thanks