21 lines
619 B
Plaintext
21 lines
619 B
Plaintext
![]() |
=== On 2015-05-08T15:31:48Z Dinesh Bolkensteyn Wrote:
|
|||
|
LGTM
|
|||
|
|
|||
|
=== On 2019-09-11T11:24:27Z Andrei Epure Wrote:
|
|||
|
\[~nicolas.harraudeau] - do you see a good reason not to raise an issue when the string is not an exact match? One could include the name of the parameter inside the message like
|
|||
|
|
|||
|
* ``++"someParameter should have value X"++``
|
|||
|
|
|||
|
or using interpolated strings
|
|||
|
|
|||
|
* ``++ $"someParameter should have value X but has value {someParameter}"++``
|
|||
|
|
|||
|
|
|||
|
|
|||
|
|
|||
|
As it is, I don't find the rule as useful as it could be
|
|||
|
|
|||
|
=== On 2019-09-11T11:42:07Z Nicolas Harraudeau Wrote:
|
|||
|
\[~andrei.epure] Both cases you mentioned make sense.
|
|||
|
|