fancy-google-docs 0.3.2__tar.gz → 0.3.4__tar.gz

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.
@@ -8,6 +8,26 @@ The four packages share one version, because they are generated from one
8
8
  `provider/` definition and a version that meant something different in each
9
9
  would be a version nobody could reason about.
10
10
 
11
+ ## [0.3.4] — 2026-09-12
12
+
13
+ ### Changed
14
+
15
+ - **Requires `fancy-connector-core` ≥ 0.4.0** — `particle-academy/fancy-connector-core` for php, `@particle-academy/fancy-connector-core` for js. The flow executors now pass a provider's declared `idempotencyMaxLength` through to the core's key derivation, and a named argument an older core does not accept is a fatal rather than a no-op, so the floor moves with it. This connector declares no limit and passes nothing, so nothing else changes for it; the bump is the floor alone.
16
+
17
+ ## [0.3.3] — 2026-09-11
18
+
19
+ ### Added
20
+
21
+ - **`fancy-flow-php` executors for every node.** `src/Flow/` carries one `#[FlowNode]` class per action and trigger, and `GoogleDocsFlow::EXECUTORS` lists them.
22
+
23
+ A Laravel host running fancy-flow-php could show this connector's nodes in its editor and could not run them: `particle-academy/google-docs-php` shipped the request builders and no executor. Each one is the PHP twin of the executor in `@particle-academy/google-docs-js` — the same kind, the same request, the same value on `out` — and an unsafe-to-replay action derives its idempotency key from the run and the node, so a retried durable run sends the key it sent the first time.
24
+
25
+ Register them by adding `vendor/particle-academy/google-docs-php/packages/php/src/Flow` to `config('fancy-flow.discover')`. `particle-academy/fancy-flow-php` is SUGGESTED, not required, and conflicts outside `>=0.51.0 <2.0`, the range the executors were tested under. Nothing outside `Flow\` needs it.
26
+
27
+ ### Fixed
28
+
29
+ - **Fake mode through `ConnectorClient` threw.** `GoogleDocs::descriptor()` handed the connector core its faker as `GoogleDocsFaker::respond(...)`, which takes `($operation, $request)`; the core calls a faker `($operation, $config, $fake, $input)`. So `$config` arrived as `$request` and every fake call died on "Call to a member function … on null". The descriptor now translates between the two. Calling `GoogleDocsFaker::respond()` directly — what this package's own tests do, which is why they never saw it — is unchanged.
30
+
11
31
  ## [0.3.2] — 2026-09-06
12
32
 
13
33
  ### Changed
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.5
2
2
  Name: fancy-google-docs
3
- Version: 0.3.2
3
+ Version: 0.3.4
4
4
  Summary: Google Docs for Python — the service descriptor, its faker, its webhook verification, and one function per operation. Plain HTTP; no vendor SDK.
5
5
  Project-URL: Homepage, https://github.com/Fancy-Friends/google-docs
6
6
  Project-URL: Issues, https://github.com/Fancy-Friends/google-docs/issues
@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
4
4
 
5
5
  [project]
6
6
  name = "fancy-google-docs"
7
- version = "0.3.2"
7
+ version = "0.3.4"
8
8
  description = "Google Docs for Python — the service descriptor, its faker, its webhook verification, and one function per operation. Plain HTTP; no vendor SDK."
9
9
  readme = "README.md"
10
10
  # 3.11 matches fancy-flow-py's floor: 3.10 reaches end of life on 2026-10-31,
@@ -21,7 +21,7 @@ from .actions.document_create import document_create
21
21
  from .faker import respond
22
22
  from .service import BASE_URLS, CONNECTOR_API_VERSION, REQUIRES, SANDBOX, SERVICE, TITLE, descriptor
23
23
 
24
- __version__ = "0.3.2"
24
+ __version__ = "0.3.4"
25
25
 
26
26
  __all__ = [
27
27
  "BASE_URLS",