I have built a native component, imported the library to Maestro and added the component to a form.
Now I need to update the component to add an attribute for 'data-ng-model', so that the field value is included in the data model, and so that validation is triggered (at least that is what I am hoping will happen).
However, I have updated library.config.xml from 1 to 1.1.0, run 'gulp zip' and now trying to import the library to Maestro.
Maestro shows an error ' version 1.0.0 already exists'.
Do I need to delete the library before importing the latest version?
What impact will that have on the component, and any other components that use the original?
Should Maestro import the new library as a new version because 1.1.0 is different to 1.0.0?
Any guidance would be appreciated.
I believe your approach to native component development may need to be updated to take into account the new library management features in the latest version of Maestro (18.05 and above).
I believe in place of the .library-config.xml file you now need to supply a lib-manifest.json file in your library structure:
The content of this lib-manifest.json file should be:
"description": "This is a library containing custom components",
"name": "My Custom Components",
It is in this file that you specify the library version.
I hope this helps!Ryan
thanks for the comments.
I haven't had a chance to revisit this for some time due to other priorities. But it is good to have something to work with.
I'll give that a try and let you know how it goes.
I've built an updated component and created a new file for 'lib-manifest.json. I removed the library-config.xml file from the src folder, and ran gulp zip to create the library package.
In lib-manifest I specify versio nas "1.1.0"; the existing version of the component in Maestro is "1.0.0".
However, when I try to import to Maestro I get an error message that says 'Library name not specified".
If I include the library-config.xml, I get an error that the library version 1.0.0 already exists.
Do you have any suggestions of the required files?
Or is there an updated KB article?. The current documentation only refers to the library-config.xml file.