caspian-utils 0.0.27 → 0.0.29
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/dist/docs/fetch-data.md +11 -9
- package/dist/docs/installation.md +1 -1
- package/package.json +1 -1
package/dist/docs/fetch-data.md
CHANGED
|
@@ -12,10 +12,10 @@ related:
|
|
|
12
12
|
- /docs/database
|
|
13
13
|
- /docs/file-uploads
|
|
14
14
|
- /docs/cache
|
|
15
|
-
- /docs/routing
|
|
16
|
-
- /docs/pulsepoint
|
|
17
|
-
- /docs/pulsepoint-runtime-map
|
|
18
|
-
- /docs/project-structure
|
|
15
|
+
- /docs/routing
|
|
16
|
+
- /docs/pulsepoint
|
|
17
|
+
- /docs/pulsepoint-runtime-map
|
|
18
|
+
- /docs/project-structure
|
|
19
19
|
- /docs/index
|
|
20
20
|
---
|
|
21
21
|
|
|
@@ -140,11 +140,11 @@ Validate incoming form and mutation payloads before persisting them. See [valida
|
|
|
140
140
|
|
|
141
141
|
If an RPC action needs transient request-scoped success or error state beyond its direct return payload, read [state.md](./state.md) and verify the current wire-request lifecycle before depending on persistence across navigations or full-page reloads.
|
|
142
142
|
|
|
143
|
-
Important:
|
|
144
|
-
|
|
145
|
-
- `pp.rpc()` posts to the current route RPC bridge.
|
|
146
|
-
- Older docs may refer to `pp.fetchFunction()`. In this repo's current runtime, the supported helper is `pp.rpc()`.
|
|
147
|
-
- Use [pulsepoint-runtime-map.md](./pulsepoint-runtime-map.md) when debugging browser-side RPC options such as streaming, upload progress, abort behavior, redirects, or SPA interaction.
|
|
143
|
+
Important:
|
|
144
|
+
|
|
145
|
+
- `pp.rpc()` posts to the current route RPC bridge.
|
|
146
|
+
- Older docs may refer to `pp.fetchFunction()`. In this repo's current runtime, the supported helper is `pp.rpc()`.
|
|
147
|
+
- Use [pulsepoint-runtime-map.md](./pulsepoint-runtime-map.md) when debugging browser-side RPC options such as streaming, upload progress, abort behavior, redirects, or SPA interaction.
|
|
148
148
|
|
|
149
149
|
## Streaming Responses
|
|
150
150
|
|
|
@@ -276,6 +276,8 @@ Use [auth.md](./auth.md) when the action should also participate in centralized
|
|
|
276
276
|
|
|
277
277
|
According to the upstream Caspian RPC docs, actions are private by default until decorated with `@rpc()`, and the framework includes CSRF protection plus origin validation for exposed actions.
|
|
278
278
|
|
|
279
|
+
For reverse-proxy deployments, RPC origin validation can also resolve the public app origin from `APP_BASE_URL`, `PUBLIC_BASE_URL`, or `SITE_URL`, and otherwise falls back to forwarded host and protocol headers when they are present.
|
|
280
|
+
|
|
279
281
|
## Serialization Rules
|
|
280
282
|
|
|
281
283
|
For RPC responses, Caspian can automatically serialize common Python return types such as:
|