Restarting Local Loops
After making changes to your Loop, here's how to reload them in Olive Helps.
Last updated
After making changes to your Loop, here's how to reload them in Olive Helps.
Last updated
The purpose of local Loops is to make it easy for authors to actively develop Loops and see/test changes immediately without having to publish them. The way Olive Helps makes it possible to reload a Loop's code is by "restarting" the Loop.
There are two options to restart your Loop:
Choose "Restart" to stop the current execution and start it again with the latest source file.
Choose "Restart with live reload" to automatically restart the Loop each time a change to the source file is detected.
"Restart with live reload" makes it possible for a Loop's changes to be detected and reloaded automatically. File watchers are created for the loop.js file and its parent directory, so that any process that recreates or writes to them will still be detected.
The idea is that from the time you save a change to any file a Loop project, the Webpack watcher rebuilds the Loop immediately, and Olive Helps detects that and restarts the Loop. Doing it this way, everything should be as quick and automatic as possible.
Refer to the steps in for how to build the Loop manually or automatically.
Live reloading is the most powerful when the instructions from the section are followed to make sure the loop.js is automatically rebuilt when Loop code is changed.
