Using the #override keyword in the header file will not delete the target namespace folder before writing to it.
To Reproduce
Add a namespace override to the project header file. (eg: #override namespace2)
Create a function within the namespace scope in your main.jmc file. (eg: function namespace2.test() {...})
Compile the project. It should generate the new namespace folder and function within it.
Go back to main.jmc and delete/comment out the function we just created.
Recompile project. The new namespace folder and function file will not be deleted.
(Optional) Add another function to the main.jmc file with a different name (eg: function namespace2.test2() {...})
(Optional) Recompile the project. The second function gets appended to the new namespace without deleting the first.
Expected behavior
The namespaces declared by the #override header keyword should be deleted prior to being written to, which isn't currently happening.
Screenshots
Desktop
Windows 10
Additional context
It should be noted this only seems to happen to namespaces that are affected by the #override header, as the main namespace used for the project is overwritten correctly.
Describe the bug
Using the
#overridekeyword in the header file will not delete the target namespace folder before writing to it.To Reproduce
main.jmcfile. (eg: function namespace2.test() {...})main.jmcand delete/comment out the function we just created.main.jmcfile with a different name (eg: function namespace2.test2() {...})Expected behavior
The namespaces declared by the
#overrideheader keyword should be deleted prior to being written to, which isn't currently happening.Screenshots
Desktop
Additional context
It should be noted this only seems to happen to namespaces that are affected by the
#overrideheader, as the main namespace used for the project is overwritten correctly.