Not: Reason: Empty or special character is detected in pair of square brackets.
But: Reason: A pair of square brackets is empty or contains not allowed characters.
Not: Slicing is currently not supported!
But: Slicing is not supported!
(no need to mention 'currently', because then customers will assume that slicing might be available in near future already)
Not: 'Invalid expression while handling the parameter '${listP.${keyP}}'.'
But: 'Invalid expression found: '${listP.${keyP}}'.'
But nevertheless: This expression itself is not really invalid. It's a data type issue: List indices are expected to be positive integers, and not strings. Later this should be reworked.
the wording needs to be adapted:
Not:
Reason: Empty or special character is detected in pair of square brackets.But:Reason: A pair of square brackets is empty or contains not allowed characters.Not:
Slicing is currently not supported!But:Slicing is not supported!(no need to mention 'currently', because then customers will assume that slicing might be available in near future already)
Not:
'Invalid expression while handling the parameter '${listP.${keyP}}'.'But:'Invalid expression found: '${listP.${keyP}}'.'But nevertheless: This expression itself is not really invalid. It's a data type issue: List indices are expected to be positive integers, and not strings. Later this should be reworked.
Originally posted by @HolQue in https://github.com/test-fullautomation/python-jsonpreprocessor/issues/238#issuecomment-2014728173