8000 [Validator] ExpressionValidator should use OBJECT_TO_STRING to allow value in message · Issue #24595 · symfony/symfony · GitHub
[go: up one dir, main page]
Skip to content
8000

[Validator] ExpressionValidator should use OBJECT_TO_STRING to allow value in message #24595

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
Hanmac opened this issue Oct 17, 2017 · 0 comments
Closed

[Validator] ExpressionValidator should use OBJECT_TO_STRING to allow value in message #24595

Hanmac opened this issue Oct 17, 2017 · 0 comments
Labels
Feature Validator

Comments

@Hanmac
Copy link
Contributor
Hanmac commented Oct 17, 2017
Q A
Bug report? no
Feature request? yes
BC Break report? no
RFC? no
Symfony version 3.3.10

ExpressionValidator should use OBJECT_TO_STRING for formatValue,
so i can use {{ value }} inside the message and it isn't replaced with just 'object'

i don't think it's more like a feature request then a pure bug,
so i didn't make a (simple) pull request jet, but wait what you guys think about it.
@Simperfit Simperfit mentioned this issue Oct 30, 2017
Merged
fabpot added a commit that referenced this issue Dec 1, 2017
@fabpot
bug #24750 [Validator] ExpressionValidator should use OBJECT_TO_STRIN…
5a6e2d7 
…G (Simperfit)

This PR was merged into the 2.7 branch.

Discussion
----------

[Validator] ExpressionValidator should use OBJECT_TO_STRING

…value in message

| Q             | A
| ------------- | ---
| Branch?       | master
| Bug fix?      | no
| New feature?  | yes
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets | #24595
| License       | MIT
| Doc PR        | Will do.

Commits
-------

7dac528 [Validator] ExpressionValidator should use OBJECT_TO_STRING to allow value in message
@fabpot fabpot closed this as completed Dec 1, 2017
4A69
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Feature Validator
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@fabpot @Hanmac @xabbuh
0