...
The meaning of the parameters is the following:
| getModules.json | ||
|---|---|---|
| Parameter | Required | Description |
| name | Yes | Module friendly name (no limitations, can be changed in time example: OMS Events module) |
| code | yes | Module internal name - This will be the entry for the service in the baseUrlRepository (see below) (no spaces, all lowercase, cannot be changed once registered, example: oms_events) |
| pages | yes | JSON array containing frontend pages data Each entity inside the array should contain the following attributes: name - Frontend friendly name (example: List events) code - Frontend internal name (example: applications) - This one should be the same with the AngularJS module name defined in the module module_link - relative (to your service) pathto the module controller JS file |
To understand more of what is happening above, have a look at the actual controller, which in our example sits in /all/applicationsController.js
...
In this example, const baseUrl would end up being "http://localhost/services/applications/". This is injected by the registry and the core automatically, you do not have to care about this. And actually you also can not care about this, as the registry sets the url for you, based on what you put in the docker-compose.yml. Also you will find the name of your controller here, hint: .moduemodule('app.applications', []). If you fuck up this configuration, you will blow the complete frontend by activating your module until https://
| Jira Legacy | ||
|---|---|---|
|
|
...