Improve formatting and consistency in configuration and documentation files

Author: Knerio

code0-tech-hercules-1.0.0.tgz

@@ -11,14 +11,14 @@ The GLS action requires a few credentials to authenticate with the GLS ShipIT AP
 
 ## Configuration reference
 
-| Config Name     | Type        | Required | Default | Description |
-|-----------------|-------------|----------|---------|-------------|
-| `client_id`     | string      | **Yes**  | —       | OAuth2 client ID for authenticating with the GLS API |
-| `client_secret` | string      | **Yes**  | —       | OAuth2 client secret for authenticating with the GLS API |
-| `contact_id`    | string      | No       | `""`    | GLS contact ID used in some API requests (see note below) |
-| `ship_it_api_url` | string    | No       | `https://api.gls-group.net/shipit-farm/v1/backend/rs` | GLS ShipIT API base URL |
-| `auth_url`      | string      | No       | `https://api.gls-group.net/oauth2/v2/token` | GLS OAuth2 token endpoint — must end in `/token` |
-| `shipper`       | GLS_SHIPPER | No       | —       | Default shipper address used when no shipper is provided in the shipment data |
+| Config Name       | Type        | Required | Default                                               | Description                                                                   |
+|-------------------|-------------|----------|-------------------------------------------------------|-------------------------------------------------------------------------------|
+| `client_id`       | string      | **Yes**  | —                                                     | OAuth2 client ID for authenticating with the GLS API                          |
+| `client_secret`   | string      | **Yes**  | —                                                     | OAuth2 client secret for authenticating with the GLS API                      |
+| `contact_id`      | string      | No       | `""`                                                  | GLS contact ID used in some API requests (see note below)                     |
+| `ship_it_api_url` | string      | No       | `https://api.gls-group.net/shipit-farm/v1/backend/rs` | GLS ShipIT API base URL                                                       |
+| `auth_url`        | string      | No       | `https://api.gls-group.net/oauth2/v2/token`           | GLS OAuth2 token endpoint — must end in `/token`                              |
+| `shipper`         | GLS_SHIPPER | No       | —                                                     | Default shipper address used when no shipper is provided in the shipment data |
 
 > **`contact_id`:** This identifier is required for certain shipment operations (e.g. end-of-day reports and some services). It is issued by GLS support — contact them directly to request it.
 

code0-tech-tucana-0.0.0.tgz

@@ -179,12 +179,12 @@ All shipment functions accept a common set of parameters in addition to their ty
 
 **Common parameters for all shipment functions:**
 
-| Parameter | Type | Required | Description |
-|-----------|------|----------|-------------|
-| `shipment` | GLS_SHIPMENT_WITHOUT_SERVICES | **Yes** | Shipment data (consignee, shipper, units, product) |
-| `printingOptions` | GLS_PRINTING_OPTIONS | **Yes** | Label format settings |
-| `returnOptions` | GLS_RETURN_OPTIONS | No | Whether to return print data and routing info |
-| `customContent` | GLS_CUSTOM_CONTENT | No | Custom logo and barcode settings |
+| Parameter         | Type                          | Required | Description                                        |
+|-------------------|-------------------------------|----------|----------------------------------------------------|
+| `shipment`        | GLS_SHIPMENT_WITHOUT_SERVICES | **Yes**  | Shipment data (consignee, shipper, units, product) |
+| `printingOptions` | GLS_PRINTING_OPTIONS          | **Yes**  | Label format settings                              |
+| `returnOptions`   | GLS_RETURN_OPTIONS            | No       | Whether to return print data and routing info      |
+| `customContent`   | GLS_CUSTOM_CONTENT            | No       | Custom logo and barcode settings                   |
 
 ---
 

docs/Actions/GLS/configs.md

@@ -27,20 +27,20 @@ Before using the GLS Action you will need:
 
 ### Hercules / Aquila
 
-| Requirement | Description |
-|-------------|-------------|
-| Running Aquila server | The action connects to Aquila on startup to register its functions |
-| `HERCULES_AUTH_TOKEN` | Auth token issued by your Aquila instance |
-| `HERCULES_AQUILA_URL` | Host and port of your Aquila server (e.g. `aquila.example.com:50051`) |
-| Docker + Docker Compose | Used to run the action as a container |
+| Requirement             | Description                                                           |
+|-------------------------|-----------------------------------------------------------------------|
+| Running Aquila server   | The action connects to Aquila on startup to register its functions    |
+| `HERCULES_AUTH_TOKEN`   | Auth token issued by your Aquila instance                             |
+| `HERCULES_AQUILA_URL`   | Host and port of your Aquila server (e.g. `aquila.example.com:50051`) |
+| Docker + Docker Compose | Used to run the action as a container                                 |
 
 ### GLS Developer Portal
 
-| Requirement | How to obtain |
-|-------------|---------------|
-| `client_id` | Create an application at [https://dev-portal.gls-group.net](https://dev-portal.gls-group.net) and find it under **My Apps** |
-| `client_secret` | Found alongside the `client_id` in **My Apps** on the GLS developer portal |
-| `contact_id` *(optional)* | Issued by GLS support — contact them directly to request it |
+| Requirement               | How to obtain                                                                                                               |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------|
+| `client_id`               | Create an application at [https://dev-portal.gls-group.net](https://dev-portal.gls-group.net) and find it under **My Apps** |
+| `client_secret`           | Found alongside the `client_id` in **My Apps** on the GLS developer portal                                                  |
+| `contact_id` *(optional)* | Issued by GLS support — contact them directly to request it                                                                 |
 
 > **Note:** The `contact_id` is required for some shipment operations. If you are unsure whether you need it, contact GLS support.
 

docs/Actions/GLS/functions.md

@@ -13,12 +13,12 @@ This guide walks you through creating your first GLS shipment using the GLS Acti
 
 Follow the [Installation Guide](../../Guides/installation.md) to deploy the GLS Action, then set the following configuration values in your Hercules admin panel (or `.env` file):
 
-| Config | Value |
-|--------|-------|
-| `client_id` | Your GLS OAuth2 client ID |
-| `client_secret` | Your GLS OAuth2 client secret |
+| Config            | Value                                                                                |
+|-------------------|--------------------------------------------------------------------------------------|
+| `client_id`       | Your GLS OAuth2 client ID                                                            |
+| `client_secret`   | Your GLS OAuth2 client secret                                                        |
 | `ship_it_api_url` | GLS ShipIT endpoint (default: `https://api.gls-group.net/shipit-farm/v1/backend/rs`) |
-| `auth_url` | GLS auth endpoint (default: `https://api.gls-group.net/oauth2/v2/token`) |
+| `auth_url`        | GLS auth endpoint (default: `https://api.gls-group.net/oauth2/v2/token`)             |
 
 See [Configuration](./configs.md) for the full list of options and how to obtain credentials.
 

docs/Actions/GLS/overview.md

@@ -111,10 +111,10 @@ A: Yes, use the `reprintParcel` function with the `TrackID` and the original `Cr
 
 ## Common error codes
 
-| Error Code | Cause | Resolution |
-|------------|-------|------------|
-| `ERROR_CREATING_GLS_SHIPMENT` | API returned an error during shipment creation or management | Check `validateShipment` output for details |
-| `INVALID_PRODUCT` | Used `"PARCEL"` product with a service that requires `"EXPRESS"` | Set `Product: "EXPRESS"` in the shipment |
+| Error Code                    | Cause                                                            | Resolution                                  |
+|-------------------------------|------------------------------------------------------------------|---------------------------------------------|
+| `ERROR_CREATING_GLS_SHIPMENT` | API returned an error during shipment creation or management     | Check `validateShipment` output for details |
+| `INVALID_PRODUCT`             | Used `"PARCEL"` product with a service that requires `"EXPRESS"` | Set `Product: "EXPRESS"` in the shipment    |
 
 ---
 
@@ -178,11 +178,11 @@ Open a pull request against the `main` branch of [code0-tech/centaurus](https://
 
 ### Development commands
 
-| Command | Description |
-|---------|-------------|
-| `npm run build` | Build all actions |
-| `npm run test` | Run the test suite |
-| `npm run test:watch` | Run tests in watch mode |
-| `npm run lint` | Run ESLint |
-| `npm run create-action -- <name>` | Scaffold a new action |
+| Command                           | Description             |
+|-----------------------------------|-------------------------|
+| `npm run build`                   | Build all actions       |
+| `npm run test`                    | Run the test suite      |
+| `npm run test:watch`              | Run tests in watch mode |
+| `npm run lint`                    | Run ESLint              |
+| `npm run create-action -- <name>` | Scaffold a new action   |