MaestroThe UI design product. | Form Builder | 18.11 This feature was introduced in 18.11.
As a general good development practice, you will want to have known good quality versions of all libraries that Form Builders and others depend on to do their work. Having good quality library versions provides these users with a level of confidence that any issues they encounter are likely to be caused by what they are doing, not by the dependent libraries they rely on. Dependent library versions, therefore, need to be immutable, and tagging a library version satisfies this requirement.
Maestro allows you to create and use tagged libraries.
A tagged library is a read-only library version that prevents any changes from being saved to the library. Tagged library versions provide an effective way of keeping a clean, final record of a library. Once a tagged library is created, it is still possible to create new library versions based on the tagged version.
We recommend creating a tagged version of a library when it's ready to be deployed into production. This ensures that you can always roll-back to a production-ready version of a library.
The tagged version of a library can be identified by the tag icon in the Navigator pane or via the Versions tab.
Although a tagged version of a library cannot be edited, you can a new version based on a tagged version and that new version will be editable.
There are a few things you need to know when you work with tagged libraries:
To create a tagged library:
Once you have created a tagged version of a library, you may need to create a new version of the library based on this tagged version.
To create a library version based on a tagged library version:
2.0.0- develop
.Next, learn about library precedence.