Calling Form->input() with 'error'=>'' should trigger field error, but not render error element.

[bar]

From #863 (comment)

The idea is to complete [1] and [2] which enabled to trigger element errors (field coloring) but not rendering error messages.

Actually, calling Form->input() with:
'error' => false prevent any kind of error reporting (field error coloring AND error messages)
'error' => '' allow field error coloring AND render an HTML element with and empty error message

IMO,
'error' => '' should allow field error coloring BUT prevent rendering an HTML element with and empty error message.

[1] 9f23f65
[2] ae8dd1c

[markstory]

Any objections to this? I think its reasonable for 2.3 It adds a bit more sensitive to the error key and empty values, but its already kind of complicated.

[lorenzo]

That is kind of complicated and magic I would never use an empty string as a configure value for anything. Is there a way we can change it to something more meaningful?

[bar]

@lorenzo you mean, using two variables?

[lorenzo]

Yeah, that might be the only solution without making option handling complicated

[bar]

👍 for that

I'm thinking something like:
'error' => false prevent any kind of error reporting (field error coloring AND error messages)
'errorMessage' => false (default: true) allow field error coloring BUT prevent rendering an HTML element with an empty error message.

[markstory]

I like the idea of an additional option as well. This makes the intent clearer and doesn't add additional behavior to various falsey values.

[bar]

Rebased to 2.3 and updated as discussed :)

[bar]

I'll update the docs if this goes through.

[ADmad]

"coloring" is not an accurate word. The wrapper div gets the error class, you could have any styling for that class.

[bar]

Ohh man, feature blindness on that one!
Fixed

[bar]

Updated again, missed a 'color' :P

[lorenzo]

I think this makes sense, merging this one