Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update vs Replace #31

Open
miola03 opened this issue Jun 18, 2021 · 0 comments
Open

Update vs Replace #31

miola03 opened this issue Jun 18, 2021 · 0 comments

Comments

@miola03
Copy link

miola03 commented Jun 18, 2021

Seems when I run the task to deploy code it does a complete replace each time and adds a new ID to the page or field interaction even on exiting scripts im tweaking slightly. Is there a way to configure this repository to look for existing scripts and update instead of do a full replace with a net new interaction ID.

EX: pushed the logger.ts script within the client-corporation\name\logger.ts which deployed no problem and had a field interaction ID of 11 then tweaked the language in the console.log, deployed again and the field interaction had an ID of 13. I didnt change the path name of the src file, the only property I changed within the script was 'enabled' from true to false as well as the previously mentioned tweak to the language in the console.log (see below)

image

Would be nice for this repository to recognize that the core of the script hasnt changed, just the contents inside therefore do an update to the existing instead deleting and adding net new in order to keep the same ID.

Let me know if im missing anything here. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant