Some checks are pending
offline / test (push) Waiting to run
Signup registers/binds a Verae central user and stores veraeUserId. Public access stays the zappier API key. Chain JWTs stay server-side behind tokenRef. Authz, billing, and jobs.watch carry veraeUserId.
45 lines
1.3 KiB
Markdown
45 lines
1.3 KiB
Markdown
# `zappier/upstream`
|
||
|
||
**Package:** `zappier`
|
||
**Source:** `packages/zappier/src/upstream.ts`
|
||
**Lines:** 48
|
||
|
||
## What this module is
|
||
|
||
Implementation module in `zappier`. The tables below are extracted from the source (signatures + JSDoc).
|
||
|
||
## Exports
|
||
|
||
`UpstreamFetch`, `proxyVerae`
|
||
|
||
## Types / interfaces / classes
|
||
|
||
| Kind | Name |
|
||
|------|------|
|
||
| type | `UpstreamFetch` |
|
||
|
||
## Functions
|
||
|
||
| Name | Parameters | Param types (JSDoc) | Returns | Calls (same file / helpers) |
|
||
|------|------------|---------------------|---------|-----------------------------|
|
||
| `proxyVerae` | `req: Request,
|
||
res: Response,
|
||
pathname: string,
|
||
fetchImpl: UpstreamFetch = fetch,` | — | `unknown` | see Call graph |
|
||
|
||
## What it imports / requires
|
||
|
||
- `express`
|
||
|
||
## Call graph (identifiers invoked)
|
||
|
||
`proxyVerae`, `replace`, `entries`, `set`, `header`, `toUpperCase`, `stringify`, `fetchImpl`, `toString`, `text`, `parse`, `isArray`, `status`, `json`
|
||
|
||
Each identifier is a call site in this file. Follow the import list to see the defining module; open that module’s MD for parameter and return types.
|
||
|
||
## Return values (how to read this)
|
||
|
||
- HTTP route handlers return Express `res.json(...)` bodies (see route docs).
|
||
- Zapier `perform` functions return a **single object** (creates) or an **array** (triggers/searches).
|
||
- Pricing functions return integer **cents** on `Quote.totalCents`.
|
||
|