issue with Parse From Developer Node

[GregoryAA]

Hello Rob,

Set in extension setup Parse From Developer Node =true

1. Add new label
   
2. Build app with Ctrl+Shift+B
3. Synchronize Translation Unit
   
4. Add developer comment and build app
   
5. Synchronize Translation Unit again
6. No changes in translation
   
7. Delete target and re-sync
8. All works as expected
   

The same situation if developer decide to change translation in comment

rebuild app and re-sync

Also could you provide the snippet for create developer comments like in AL Language Tools extension

[rvanbekkum]

Dear @GregoryAA,
Thank you for reporting this issue.

To summarize, we have the following three points to address:

1. "Parse from Developer Note" should copy the translation from the Developer note also in case that a trans-unit already exists with target state="needs-translation". This sounds logical, I'll look into it.
2. "Parse from Developer Note" is currently not copying a new translation from the Developer note if a translation already exists. This was actually intentional, but I can also see why you'd want to have the translation always updated from the Developer note (if it exists). Perhaps I could add an option, like parseFromDeveloperNoteOverride that will toggle this behaviour. What do you think? If you have other ideas, please share! :)
3. This would be an AL-specific feature, but I think I'd could add this specific feature. Can you share some ideas of how you'd like this snippet to work?

[GregoryAA]

Hello Rob,

2. Maybe you could add new action "Update Translation from Dev. node" in the context menu under Synchronize Translation Unit? It seems to me that such an opportunity should always be at hand with the developer.
   

• user enters text tcommetwithtranslation
• selects a snippet from the context menu
  

-VS code inserts text: comment = 'LanguageCode=YourLanguageText'

• after inserting the snippet, the LanguageCode area becomes active, where the user enters, for example nl-NL and then press TAB, the area YourLanguageText is activated and user enters the translation.

also maybe you can add another snippets for label, tooltip, caption.

tLabelwithComment
LabelName: Label 'EnglishText', comment = 'LanguageCode=YourLanguageText';

tTolTipwithComment
ToolTip = 'EnglishText', comment = 'LanguageCode=YourLanguageText';

tCaptionwithComment
Caption = 'EnglishText', comment = 'LanguageCode=YourLanguageText';

Often, programmers work with one language for translation. It would be nice to save the code of this language in the settings. Then using these snippets we could only enter the translation and the language code would be inserted by default

like this:
comment = 'nl-NL=YourLanguageText'

[rvanbekkum]

The changes are shipped in version 0.3.8.
Please see the CHANGELOG and the README for the details.