Hi,
I'm trying to customize intergrated-styleguide for our project.
In some cases, I want to check multiple values of an attribute,. E. g. 'test_1,test_2,test_3' and it works fine. But when I wanted to give the user the possibility for choosing which value should be inserted, I faced the following problem with quick Fixes:
Before using the abstract patterns I implemented such fixes in the way that for every option I coded a separate sqf:fix/ . But with abstract patterns it is not possible to forecast how many attrbitue values will I get.
One work-around could be implementig a separate rule for avery allowed attribute value in the DITA document.
Another work-around is estimate the number of possible attribute values, encode this number of sqf:fix/ elements with the attribute use-when="tokenize('$attrValue', ',')[1] != ''" and increment the number in [].
Both don't look well enough for me.
Did anybody already faced this problem?
Hi,
I'm trying to customize intergrated-styleguide for our project.
In some cases, I want to check multiple values of an attribute,. E. g. 'test_1,test_2,test_3' and it works fine. But when I wanted to give the user the possibility for choosing which value should be inserted, I faced the following problem with quick Fixes:
Before using the abstract patterns I implemented such fixes in the way that for every option I coded a separate sqf:fix/ . But with abstract patterns it is not possible to forecast how many attrbitue values will I get.
One work-around could be implementig a separate rule for avery allowed attribute value in the DITA document.
Another work-around is estimate the number of possible attribute values, encode this number of sqf:fix/ elements with the attribute
use-when="tokenize('$attrValue', ',')[1] != ''"and increment the number in [].Both don't look well enough for me.
Did anybody already faced this problem?