@7365admin1/core 3.52.3-staging.243 → 3.52.3-staging.244
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/.changeset/visitor-invite-type-default.md +12 -0
- package/dist/index.js +2551 -2548
- package/dist/index.js.map +1 -1
- package/dist/index.mjs +2551 -2548
- package/dist/index.mjs.map +1 -1
- package/package.json +2 -2
- package/test/visitor-invite-schema.test.mjs +77 -0
|
@@ -0,0 +1,12 @@
|
|
|
1
|
+
---
|
|
2
|
+
"@7365admin1/core": patch
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
Default the visitor-invite `type` to `guest` so already-installed resident app builds can invite again.
|
|
6
|
+
|
|
7
|
+
`POST /api/visitor-transactions/invite/:inviterId` made `type` a required field when the
|
|
8
|
+
contractor invite was added. Every resident app build already in the stores sends no `type`, so
|
|
9
|
+
those users get a 400 — `"type" is required` — on a form that has no Type field. `type` now
|
|
10
|
+
defaults to `guest`, which is exactly what the endpoint did before the contractor work.
|
|
11
|
+
Contractor invites are unchanged: `contractorType` is still required when `type` is `contractor`,
|
|
12
|
+
and an unrecognised `type` is still refused.
|