You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The extraction finds the texts for AA0, AA2, AA3 and AA6.
Based on #329 it is to be expected that AA1 is not evaluated.
But while AA2 was previously recognized, the same format does not work any more for AA4 and AA5. And only AA6 did work again.
Expected Results
The texts AA0 through AA6, except for AA1, should be found.
It seems, that this problem occurs solely for js template extractions belonging to an html attribute enclosed by quote signs. The parse_template_string function explicitely skips all content inside quotes. Shouldn't the ${} clause always be handled, since an interruption of the template string is already not handled by the parse_template_string function?
I have gotten no problems for now, overwriting the parse method with a slightly customized one in this form, ignoring the quote handling
Overview Description
The text extraction fails, after a html attribute localization in quoted signs.
Steps to Reproduce
Run extraction on the following javascript template string code:
Actual Results
The extraction finds the texts for AA0, AA2, AA3 and AA6.
Based on #329 it is to be expected that AA1 is not evaluated.
But while AA2 was previously recognized, the same format does not work any more for AA4 and AA5. And only AA6 did work again.
Expected Results
The texts AA0 through AA6, except for AA1, should be found.
Reproducibility
Always
Additional Information
babel.cfg
The text was updated successfully, but these errors were encountered: