Contact details
No response
What the essence of the bug
If you start up the plugin, you can see that "use default" extensions is not accurate to the boolean value (when input field must be hidden, it has style "flex" and i.e.).
This issue occurs because UNITADE "tries" to show/hide this input field ignoring status of just code editor extension, making it "double show/hide" resulting in unstable behaviour.
To fix this issue, you need to create an "if-statement" which checks if code editor module is enabled at all, fixing visual bug altogether.
Obsidian setup information
Non-required.
Obsidian logs
Non-required.
Version of an project's essence
3.2.6
On what OS you have encountered the bug.
Not important
Code of conduct
Issue policy
Contact details
No response
What the essence of the bug
If you start up the plugin, you can see that "use default" extensions is not accurate to the boolean value (when input field must be hidden, it has style "flex" and i.e.).
This issue occurs because UNITADE "tries" to show/hide this input field ignoring status of just code editor extension, making it "double show/hide" resulting in unstable behaviour.
To fix this issue, you need to create an "if-statement" which checks if code editor module is enabled at all, fixing visual bug altogether.
Obsidian setup information
Non-required.
Obsidian logs
Non-required.
Version of an project's essence
3.2.6
On what OS you have encountered the bug.
Not important
Code of conduct
Issue policy