As Wappler grows in popularity and adoption, it's increasingly becoming a critical part of production employments. With that comes great power and responsibility.
I support a number of client projects which effectively are fixed at a specific Wappler version, with specific Wappler module versions. In these projects I am continually having to roll-back Wappler file changes in Git, in order to preserve file versions which are tried and tested. The intent is not to keep rolling-back these updates forever. However, when I'm working on critical features, in complicated applications, the last thing I want is to introduce unnecessary file updates. These types of updates will be done in a dedicated feature, with dedicated testing.
Can we have the ability to switch off these updates in Wappler until we purposely choose to accept them?
Hmmm, have you restarted Wappler after turning it off? If it is off you should only get that when you click on the update project tool manually.When do you get that window?
Sorry but both are talking about different things..
What @brad says is: your assets wont be updated unless you manually do it with the project updater popup which he shows you how to no auto-show that popup on start..
Your screenshot:
Is about the git panel and there's a bug where you can't clean via UI new files (you can still use git commands on terminal)
Patrick says the team is already working on a fix, probably will be released soon..
@franse you are absolutely correct. It only seems to apply to new files. Hopefully Patrick will solve it as I'm continually having to ignore/dismiss these files. [edit - what I meant to say was, I don't want these new files until I choose to accept them!]
@brad here's a video showing the issue after a restart of Wappler. The window on the right is GitHub Desktop.
I've reverted this back to a feature request as the ability to stop the new files from appearing doesn't seem to turned off with the Auto Project Updater switch. Hope that's ok as the title of this features says "all files" and not just "existing files"
@scottclee but what you're showing has nothing to do with Wappler auto updating files..
It's in fact a bug of the git panel which has been reported by me and other users a few times..
This is the popup that allows you to update your files:
What you're seeing is: new files on the project, which are there on your project, but not updated to git, so Wappler is asking you to commit them to later do some push..
Wappler should understand that you don't want them on your git repo, but it clearly don't understand.. and that's why it's a bug..
Since you can't ignore them beacuse it's a bug, Wappler will ask you every time if you want to commit them again and again...
I'm pretty sure I don't use any of these new files. In fact, I discard them all before I push a release. If I want them to be added as new files to my project then I surely I should be prompted first?
You are 100% sure that your files on your projects were not updated to latest by you?
Not talking about your github repo, but if you update your assets:
I don't recall updating to latest by myself at any point in the past, but I guess I may have done so accidentally. What I do know, is that if I revert the new files in GitHub Desktop then they no longer exist. Then, once I restart Wappler it will copy them back in. This is shown in the terminal example below:
% git status
On branch master
Your branch is up to date with 'origin/master'.
nothing to commit, working tree clean
% ls lib/auth/provider_experimental.js
ls: lib/auth/provider_experimental.js: No such file or directory
[Now I restart Wappler]
% ls lib/auth/provider_experimental.js
lib/auth/provider_experimental.js
[This file now exists after the restart]
% git status
On branch master
Your branch is up to date with 'origin/master'.
Untracked files:
(use "git add ..." to include in what will be committed)
lib/auth/provider_experimental.js
lib/core/base32.js
lib/modules/csrf.js
lib/modules/otp.js
lib/modules/passkeys.js
lib/modules/ratelimit.js
public/dmxAppConnect/dmxMediumEditor/dmxMediumEditor.js.map
public/dmxAppConnect/dmxMediumEditorImageUpload/dmxMediumEditorImageUpload.js.map
nothing added to commit but untracked files present (use "git add" to track)
So clearly Wappler is adding them back in, but I guess I may have earlier accepted these modules and so they're stored as a dependency in a config file somewhere(?) and Wappler is just bringing them back in as it thinks I need them.
You mean you will never be able to push them?
In this case what I sometimes do when I have some conflict is: Backup all
Clean -f so all changes are discarded..
Then git add all --all
Git push -f
Not exactly sure if it's the best action here..
Honestly not an expert using git..
But I think you can solve it with some workaround..
Check what you think is the best option until this bug is solved..
I’ve ended up running a windows powershell script just before I publish, which overwrites the dmxConnectLib and dmxAppConnect folders with ones I have copied and saved from the right version of Wappler.
That way if I had accidentally done some kind of update, I know it won’t be included.
Not ideal, but it is my guarantee of a consistent Wappler framework on all published code!
