We’re using custom versions of dmxBootstrap4Navigation.js. Each time we open a project after a Wappler-Update the navigation of the Website is auto-broken because Wappler updates dmxBootstrap4Navigation.js.
Please implement a configuration uption to prevent auto-update of dmxBootstrap4Navigation.js (and similar files)
What if there are new features and bugs fixes that are needed in those files?
Can’t you use GIT for your use case?
Right now Wappler overwrites the file in any case even if it has not been updated. So it would be good to have the exclude function together with an Wappler update info that the excluded file has been updated and should be implemented/uploaded to the project.
@swf, I really do not see this happening, but I could be wrong.
If you want to use a custom version of a core Wappler js, would it not be better to just rename the custom file so it is not overwritten? For example, dmxBootstrap4Navigation1.js ?
If Wappler allowed users to prevent certain files from being updated, then that could cause a huge headache for the Wappler team when trying to diagnose problems and prevent and future updates for those types of files.
Maybe this might be the better way, thanks scott
Hopefully this is a solution, but I think Wappler will automatically add its own .js files, depending on the components used - so you'll have two versions, which will probably be a problem.
My thought process would be (if I were to do it) would be this:
That way you get the ease of use of Wappler and the convenience of your custom file.
I think as soon as you save the file, Wappler will add its own version, below your custom one. I’m not sure if this happens with every js file/component, but it certainly happens with some.