Describe the bug
This plugin constantly parses .jdl files to produce a .png, regardless of whether or not the file has been changed or if it has already produced a .png. Additionally there is no way to disable this behavior. If the .png file is added tyo source control, it causes issues attempting any operation in git until after closing the .jdl file AND closing VS Code itself (as it continues to parse the jdl and modify the .pdf until VS Code itself is closed).
This is a serious issue which make this plugin mostly unusable!
To Reproduce
Steps to reproduce the behavior:
Create or open a .jdl file
Watch VS Code's CPU usage spike
Add the .png file to git if it has not already been added
Close the .jdl file
Attempt to check in or revert the changes to the .png file.
Git will often, but not always, fail due to the .png file being modified by the process that continually runs in the background until VS Code is closed.
Expected behavior
I expect the .png file to only be generated if the .jdl file has actually been changed.
Failing that (and/or additionally) I expect there to be a setting that can be changed by the user to disable generating the .png file and a method to manually generate it instead.
Desktop (please complete the following information):
OS: Windows 10
Browser N/A
Version 2.6.0
Additional context
The main problem is this plugin constantly parsing the jdl file and generating a pdf file with no way to stop it.
This defiantly increases CPU usage on the machine and slows everything down.
Additionally it often interferes with git and other tools as the pdf file is opened and being modified by this process or has been modified yet again, preventing other actions, especially with other tools such as jhipster. While that can be gotten around by closing all .jdl files AND closing VS Code, it is extremely irritating.
I do not see why there can not at least be a setting to allow the user to enable/disable this behavior.
OmarHawk
commented
1 month ago
Describe the bug This plugin constantly parses .jdl files to produce a .png, regardless of whether or not the file has been changed or if it has already produced a .png. Additionally there is no way to disable this behavior. If the .png file is added tyo source control, it causes issues attempting any operation in git until after closing the .jdl file AND closing VS Code itself (as it continues to parse the jdl and modify the .pdf until VS Code itself is closed).
This is a serious issue which make this plugin mostly unusable!
To Reproduce Steps to reproduce the behavior:
Expected behavior I expect the .png file to only be generated if the .jdl file has actually been changed. Failing that (and/or additionally) I expect there to be a setting that can be changed by the user to disable generating the .png file and a method to manually generate it instead.
Desktop (please complete the following information):
Additional context The main problem is this plugin constantly parsing the jdl file and generating a pdf file with no way to stop it. This defiantly increases CPU usage on the machine and slows everything down.
Additionally it often interferes with git and other tools as the pdf file is opened and being modified by this process or has been modified yet again, preventing other actions, especially with other tools such as jhipster. While that can be gotten around by closing all .jdl files AND closing VS Code, it is extremely irritating.
I do not see why there can not at least be a setting to allow the user to enable/disable this behavior.