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
When we warmup our web app, we have folders that we want to include in the translation extractor dirs, but not yet available at the time of warming up. I believe that the step to check for these folders should be done only when we explicitly run the extractor
Actual behavior
Right now we get exception because the folders do not yet exist
Steps to reproduce
Config a list of dirs that do not exist.
The text was updated successfully, but these errors were encountered:
I can confirm that issue. The main problem is that the context from which the console is executed and the web context are different. If a path is available from one, it is not from the other. Given that the extract command is executed from CLI, web will fail.
Expected behavior
When we warmup our web app, we have folders that we want to include in the translation extractor dirs, but not yet available at the time of warming up. I believe that the step to check for these folders should be done only when we explicitly run the extractor
Actual behavior
Right now we get exception because the folders do not yet exist
Steps to reproduce
Config a list of dirs that do not exist.
The text was updated successfully, but these errors were encountered: