Open jaapio opened 4 years ago
@jaapio do you still need any help with this issue ?
If so I might have a candidate fix to contribute.
It involves loosening up a bit the regexp in DescriptionFactory::lex()
so that the tag is properly matched up all the way to the last closing brace. That would allow nested braces inside the tag description without compromising any other test afaik. Would that be an acceptable solution ?
Even with that out of the way though, I'm still losing the trailing space between the closing braces in the provided test somewhere. Still investigating why that happens, any idea ?
Even with that out of the way though, I'm still losing the trailing space between the closing braces in the provided test somewhere. Still investigating why that happens, any idea ?
From what I've found, this secondary issue originates from the trim()
call in StandardTagFactory::create()
but this seems to be intended behavior (removing the trim() call fixes it but also breaks two other tests related to this class). So I guess the test caseshould expect the tag output in the rebuilt description to be trimmed, and needs to be changed acordingly. Thoughts ?
If you think you have a way to solve this, please create a PR. We can discuss the details later.
In general, we should be able to fix issues without breaking tests because people might use the situations that are tested. That's why the tests are there. Unless we can prove that the test case was invalid.
Thanks, please review the WIP fix at #258 . It took me quite a while to come up with deleting this character :+1:
if description of inline tags not auto trimmed, then test failed because you miss whitespace: new Description('This contains {braces}')
, valid: new Description('This contains {braces} ')
Given the following test case, our Description doesn't work as expected with nested braces in inline tags.