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
Currently when parsing files built by WebPack some translator's comments aren't being picked up yet due to how webpack outputs these.
For example:
It seems WebPack will always attach comments to the previous statement rather than prepend them.
JS parsing should either be updated to correctly identify these translator's comments or it should be investigated if WebPack can be configured to correctly output comments and in this case documentation published on how to do this.
The text was updated successfully, but these errors were encountered:
JS parsing should either be updated to correctly identify these translator's comments or it should be investigated if WebPack can be configured to correctly output comments and in this case documentation published on how to do this.
I prefer the latter.
Even better would be if we could actually parse the source files for core, otherwise the source code reference is pretty much useless for translators. But that's something for another issue :-)
Currently when parsing files built by WebPack some translator's comments aren't being picked up yet due to how webpack outputs these.
For example:
It seems WebPack will always attach comments to the previous statement rather than prepend them.
JS parsing should either be updated to correctly identify these translator's comments or it should be investigated if WebPack can be configured to correctly output comments and in this case documentation published on how to do this.
The text was updated successfully, but these errors were encountered: