@tarileo/avileo-catalog-cli 0.3.16 → 0.4.0
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 +25 -0
- package/dist/index.js +449 -55
- package/dist/index.js.map +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -82,6 +82,31 @@ profile-update.json`. Without `--apply` the command returns a local diff; with
|
|
|
82
82
|
`--apply` it creates a `business.profile.update` proposal. After approval, run
|
|
83
83
|
`operation apply <id> --json` and re-read the profile.
|
|
84
84
|
|
|
85
|
+
Appointment-domain resources follow the same preview/`--apply`/approve/apply
|
|
86
|
+
sequence, but writes have no dedicated mutation route: create the proposal
|
|
87
|
+
with `--apply`, then run `operation apply <id> --json` to execute it (same as
|
|
88
|
+
`business profile update`).
|
|
89
|
+
|
|
90
|
+
- `services list [--include-inactive] --json`, `services show <id> --json`,
|
|
91
|
+
`services create|update|deactivate --from <json-file> [--apply] --json`.
|
|
92
|
+
- `professionals list [--include-inactive] --json`,
|
|
93
|
+
`professionals show <id> --json`,
|
|
94
|
+
`professionals create|update|deactivate --from <json-file> [--apply] --json`.
|
|
95
|
+
- `availability show <professionalId> --json` returns the weekly schedule and
|
|
96
|
+
upcoming exceptions; `availability set <professionalId> --from <json-file>
|
|
97
|
+
[--apply] --json` replaces the weekly schedule;
|
|
98
|
+
`availability exceptions-set <professionalId> --from <json-file> [--apply]
|
|
99
|
+
--json` replaces upcoming exceptions. There is no professional↔service
|
|
100
|
+
assignment in this domain: any active professional can be booked for any
|
|
101
|
+
active service.
|
|
102
|
+
- `agenda --date YYYY-MM-DD [--to YYYY-MM-DD] [--professional-id <id>] --json`
|
|
103
|
+
reads one day, or loops client-side over each day up to 31 days when `--to`
|
|
104
|
+
is given (there is no server-side range endpoint).
|
|
105
|
+
- `storefront status --json` reads the publication snapshot;
|
|
106
|
+
`storefront publish [--slug <slug>] [--apply] --json` and
|
|
107
|
+
`storefront unpublish [--apply] --json` propose
|
|
108
|
+
`storefront.publication.set`.
|
|
109
|
+
|
|
85
110
|
## Kuati on the existing retail cell (`tienda`)
|
|
86
111
|
|
|
87
112
|
Kuati uses the existing Tiendas deployment, API, account and data boundaries.
|