Add extendParams

[beshur]

Problem: as per request of our team, we need to add custom prefix and postfix to strings, while using accented strategy.

In this pull-request I added the extendParams option to start command, as well as in CLI.

[tryggvigy]

Hey @beshur! What use-cases do you have for the prefix and postfix? Can you give an example?

[beshur]

Hi! Our QA team requested explicit prefix and suffix [!- and -!] to distinguish from possible dynamic data in page.

…

On Fri, 25 Nov 2022, 13:53 Tryggvi Gylfason, ***@***.***> wrote: Hey @beshur <https://github.com/beshur>! What use-case s do you have for the prefix and postfix? Can you give an example? — Reply to this email directly, view it on GitHub <#55 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEB6MKDMJW4S4SEAF5OWQLWKCSEVANCNFSM6AAAAAARP5U6S4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[tryggvigy]

@beshur which pseudo-localization method are you using? Are you dynamic pseudo localization all text on the page via the start() method or are you applying pseudo localization only to your own app strings via pseudoLocalize()?

Our QA team requested explicit prefix and suffix [!- and -!] to distinguish
from possible dynamic data in page.

Are the app strings not easily distinguishable from dynamic content already due to the pseudo localization (all the added accents and elongation)?

I'm trying to understand your usecase better. Perhaps adding support for a function to post-process the pseudo-localized strings could be possible. That way you could add you own pre- and post-fixes.

[beshur]

I'm using pseudo-localization for the strings, with pseudoLocalize().

Are the app strings not easily distinguishable from dynamic content already due to the pseudo localization (all the added accents and elongation)?

I guess our QA team is following the best practices from other people.
It's definitely much easier to distinguish when it the strings are wrapped with [!- -!].

Perhaps adding support for a function to post-process the pseudo-localized strings could be possible

Yes, of course, but since there is already prefix and postfix options in the strategies, I could not see why I should not use those.