Overwriting code written outsid eof pinegrow is a scarey proposition

Feature Request
1

@matjaz

I think this is super important and should be added. I think this wording is confusing when exporting

" Do you want to overwrite the following files in folder /Users/XXXX/Local Sites/mywebsite/app/public/wp-content/themes/mytheme/?

It looks like these files were modified since you last exported them.

I think it should say something like the following:

" Do you want to overwrite the following files in folder /Users/XXXX/Local Sites/mywebsite/app/public/wp-content/themes/mytheme/?

It looks like these files were modified in a separate code editor since you last exported them. Realize that by clicking the box you will overwrite all of the files.

I think you should also add an ignore function like in GitHub that will ignore the files you coded separately in VScode. I think the ability to do VScode and Pinegrow is vital.

i just find something like this to be scary. If you think about a week earlier I did the changes in VScode i then come back to compile in PG and I am thinking what did I do?

Or even a revisions comparison like in WordPress?

strong text

2

Have made the notice more clear:

It looks like these files were modified since you last exported them. Did you use a code editor to edit the files in the exported folder? Exporting the files will overwrite any such changes.

Note, it is best to keep all project files in the source folder (including any custom files) and then export them to the target project. Never edit files directly in the export folder.

1 Like