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.
1.4 KiB
1.4 KiB
verae-zapier-middleware/lib/identity
Package: verae-zapier-middleware
Source: packages/verae-zapier-middleware/src/lib/identity.js
Lines: 17
What this module is
Implementation module in verae-zapier-middleware. The tables below are extracted from the source (signatures + JSDoc).
Exports
normalizeVeraeUsername, stableVeraeUserId
Types / interfaces / classes
None extracted.
Functions
| Name | Parameters | Param types (JSDoc) | Returns | Calls (same file / helpers) |
|---|---|---|---|---|
normalizeVeraeUsername |
username |
— | unknown |
see Call graph |
stableVeraeUserId |
username |
— | unknown |
see Call graph |
What it imports / requires
node:crypto
Call graph (identifiers invoked)
normalizeVeraeUsername, trim, toLowerCase, stableVeraeUserId, createHash, update, digest, slice
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
performfunctions return a single object (creates) or an array (triggers/searches). - Pricing functions return integer cents on
Quote.totalCents.