Update Project from Template
This articles shows you how to get the latest updates from the templates inside your project.
Update Checking the Changes
The Torizon VS Code templates are updated frequently to add new features and fix bugs. To update your project to the latest template version, follow the steps below:
- Open the project folder in VS Code.
- Run the
try-update-templatestask, clicking on it from
This will start the update process. If the updater finds a new version of some file it will open a diff window showing the changes, and will stop the updater execution. The left side of the diff tab is the newest version of the file, and the right side is the current version of the file in your project.
You can choose to keep the current version of the file simply by closing the diff tab.
If you want to update the file you need to first accept the changes, one by one, by clicking on the arrow icon on the middle of the two files, this will move the change from the left to the right (from the new to the current version):
A lot of the files from project templates are designed to be free editable by the user, so the updater will not overwrite them. So pay attention when trying to update the project to the latest from templates, to change only what is needed. The files that are not designed to be editable by the user, mainly the files from
.conf folder, will be overwritten by the updater.
You can also navigate between changes by clicking on the arrows on the top of the diff tab, the
Previous Change and
Next Change buttons:
As soon as you have all the changes that you want accepted, you can save the file and close the diff tab. This will proceed with the updater execution.
Make sure to save the file before closing the diff tab, otherwise the changes accepted will be lost. Will be necessary run the task again.
Update Accepting All Changes
If you want to accept all changes from the new version of the template, you can run the
try-update-template-accepting-all task, clicking on it from
Running this task will not show the diff tab, and will accept all changes from the new version of the template. This task is useful if you want to update the project to the latest version of the template, and you are sure that you don't have any changes that you want to keep.
The task will ask for the user confirmation before proceeding with the update: