@pipe0/base 0.2.0 → 0.3.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/CHANGELOG.md +10 -0
- package/dist/index.d.mts +789 -192
- package/dist/index.mjs +10 -10
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,15 @@
|
|
|
1
1
|
# @pipe0/ops
|
|
2
2
|
|
|
3
|
+
## 0.3.0
|
|
4
|
+
|
|
5
|
+
### Minor Changes
|
|
6
|
+
|
|
7
|
+
- f4069e3: Add `people:eventguests:luma@1` search — fetches all guests of a Luma event using the user's own Luma API key, with cursor pagination, an `approval_status` filter, and an `event_id` picker populated from the user's Luma calendar. Expands each guest into `name`, `email`, `luma_id`, `registered_at`, and a `luma_event_guest_match` JSON field.
|
|
8
|
+
|
|
9
|
+
Adds reusable "custom API keys for searches" support: `searchesRequiredConnectorInput()` / `searchesOptionalConnectorInput()` render the bring-your-own-key connector input in search forms, and a per-user-credential field-context path (`searchesContextSelectInput` + `/search/field-context`) lets a search dropdown load options via the user's connection — mirroring the existing pipe field-context system. Adds the `luma` provider. BYO-key-only pipes and searches are now previewable in sandbox.
|
|
10
|
+
|
|
11
|
+
The existing crustdata, amplemarket, and parallel searches now also render the connections card via `searchesOptionalConnectorInput()` — previously they accepted a custom connection in the payload but never surfaced an input for it in the form.
|
|
12
|
+
|
|
3
13
|
## 0.2.0
|
|
4
14
|
|
|
5
15
|
### Minor Changes
|