A connector manifest is composed of several other manifests, this allows you granular and modular design and control over your connector and the current version, exposing only the features you want to your designers.
Optionally you can add the Array of manifests directly in your Connector mannifest property whenever that makes sense.
Maintenance
Through this model you can optimize the maintenance of your code by simply adding the dependencies as git libraries and the manifests to interact with your code, that way your code is paradigmatic free and the manifests work as a facade for your code.
JSON Structure
{
"title" : string // title of your connector
"version" : string // version of your connector
"description": string // description of your connector
"backend_manifest":{
"package_name": string //backend package name
"git_url": string // backend git url
},
"actions_manifest" : [
{
"path" : string //path to your file
"name" : string //name of your file containing your actions
}
],
"events_manifest" : [
{
"path" : string //path to your file
"name" : string //name of your file containing your actions
}
],
"scripts_manifest" : [
{
"path" : string //path to your file
"name" : string //name of your file containing your actions
}
],
"queries_manifest" : [
{
"path" : string //path to your file
"name" : string //name of your file containing your actions
}
],
"components_manifest" : [
{
"path" : string //path to your file
"name" : string //name of your file containing your actions
}
],
"dependencies": [
{
"alias" : "axios",
"version" : "^0.27.2",
"path": "axios",
"packageName" : "axios"
}
]
}