@veeroute/lss-studio-angular 7.38.3336 → 7.39.3350
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md
CHANGED
|
@@ -1,8 +1,8 @@
|
|
|
1
|
-
# @veeroute/lss-studio-angular@7.
|
|
1
|
+
# @veeroute/lss-studio-angular@7.39.3350
|
|
2
2
|
|
|
3
3
|
Programming interface for the Veeroute Studio tool. # Description The server side of Veeroute Studio. ## Reserved attributes These attribute keys are reserved for specific business logic: | Attribute key | Parent entity | Purpose | | ---------------------| ----------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | `ICON_NAME` | location | The attribute value is written into the `web_location_geopoint.icon_name` field | | `FORCED_GEOPROVIDER` | geo_settings | The attribute value defines the geo data provider used for drawing trips on the map; it will be used instead of the value specified in `plan_settings.geo_settings.geo_provider` | | `TRIP_VERIFIED` | trip | The attribute value indicates whether the trip has been verified and approved manually | Usage example — overriding the geo provider for drawing trips in Studio: { \"plan_settings\": { \"geo_settings\": { \"attributes\": [ { \"key\": \"FORCED_GEOPROVIDER\", \"value\": \"OSRM_EXTERNAL\" } ] } } } ## Additional attributes Rules for processing additional attributes when using Universal Extension: * If the entity key does not exist — such an additional attribute is ignored * If the attribute key for the entity already exists — the attribute value will be overwritten after the calculation finishes ## Roles Restrictions on working with a virtual folder: * After creation, a folder cannot change its owner or company. * When a new folder is created not in ROOT, it inherits the owner and the company from the parent folder. Effect of the account role on the virtual file system: ### ADMIN, PARTNER, USER, BOT * Access only to one\'s own folders (`folder.owner_username = account.username`) and to files inside those folders * Ability to open any other user\'s files for editing via a direct file link ### COMPANYOWNER * Access only to folders of one\'s own company (`folder.owner_company_key = account.company_key`) and to files inside those folders * Ability to open any other user\'s files for editing via a direct file link ### OVERLORD * Access to all folders in the environment (`folder.owner_company_key = *`) and to files inside those folders ## Entity diagram 
|
|
4
4
|
|
|
5
|
-
The version of the OpenAPI document: 7.
|
|
5
|
+
The version of the OpenAPI document: 7.39.3350
|
|
6
6
|
|
|
7
7
|
## Building
|
|
8
8
|
|
|
@@ -24,7 +24,7 @@ Navigate to the folder of your consuming project and run one of next commands.
|
|
|
24
24
|
_published:_
|
|
25
25
|
|
|
26
26
|
```console
|
|
27
|
-
npm install @veeroute/lss-studio-angular@7.
|
|
27
|
+
npm install @veeroute/lss-studio-angular@7.39.3350 --save
|
|
28
28
|
```
|
|
29
29
|
|
|
30
30
|
_without publishing (not recommended):_
|