@executor-js/plugin-graphql
1.5.27
Patch Changes
- Updated dependencies [
c7ab1e2]:- @executor-js/api@1.4.47
- @executor-js/react@1.4.47
- @executor-js/sdk@1.5.27
- @executor-js/config@1.5.27
1.5.26
Patch Changes
- Updated dependencies []:
- @executor-js/sdk@1.5.26
- @executor-js/config@1.5.26
- @executor-js/api@1.4.46
- @executor-js/react@1.4.46
1.5.25
Patch Changes
- Updated dependencies []:
- @executor-js/sdk@1.5.25
- @executor-js/config@1.5.25
- @executor-js/api@1.4.45
- @executor-js/react@1.4.45
1.5.24
Patch Changes
- Updated dependencies []:
- @executor-js/sdk@1.5.24
- @executor-js/config@1.5.24
- @executor-js/api@1.4.44
- @executor-js/react@1.4.44
1.5.23
Patch Changes
-
#1199
29936d5Thanks @RhysSullivan! - Fix the GraphQL plugin generating invalid operations against large schemas, and make field selection caller-controlled instead of a baked-in guess.Previously each tool froze a recursive, depth- and count-bounded selection at sync time. Against a rich schema (GitLab) this produced invalid GraphQL (composite fields with no sub-selection, nested fields missing required arguments) so every call over a rich return type failed, and the arbitrary bound silently truncated which fields came back.
Generated tools now default to selecting only scalar/enum leaf fields of the return type (always valid, always within a server's query-complexity budget), and expose an optional
selectinput carrying a GraphQL selection set so a caller can request nested or list data per call (including supplying nested required arguments). Fixes #1146. -
Updated dependencies [
29936d5,29936d5]:- @executor-js/api@1.4.43
- @executor-js/react@1.4.43
- @executor-js/sdk@1.5.23
- @executor-js/config@1.5.23
1.5.22
Patch Changes
- Updated dependencies []:
- @executor-js/sdk@1.5.22
- @executor-js/config@1.5.22
- @executor-js/api@1.4.42
- @executor-js/react@1.4.42
1.5.21
Patch Changes
- Updated dependencies []:
- @executor-js/sdk@1.5.21
- @executor-js/config@1.5.21
- @executor-js/api@1.4.41
- @executor-js/react@1.4.41
1.5.20
Patch Changes
- Updated dependencies []:
- @executor-js/sdk@1.5.20
- @executor-js/config@1.5.20
- @executor-js/api@1.4.40
- @executor-js/react@1.4.40
1.5.19
Patch Changes
- Updated dependencies []:
- @executor-js/sdk@1.5.19
- @executor-js/config@1.5.19
- @executor-js/api@1.4.39
- @executor-js/react@1.4.39
1.5.18
Patch Changes
- Updated dependencies []:
- @executor-js/sdk@1.5.18
- @executor-js/config@1.5.18
- @executor-js/api@1.4.38
- @executor-js/react@1.4.38
1.5.17
Patch Changes
- Updated dependencies []:
- @executor-js/sdk@1.5.17
- @executor-js/config@1.5.17
- @executor-js/api@1.4.37
- @executor-js/react@1.4.37
1.5.16
Patch Changes
- Updated dependencies []:
- @executor-js/sdk@1.5.16
- @executor-js/config@1.5.16
- @executor-js/api@1.4.36
- @executor-js/react@1.4.36
1.5.15
Patch Changes
- Updated dependencies []:
- @executor-js/sdk@1.5.15
- @executor-js/api@1.4.35
- @executor-js/config@1.5.15
- @executor-js/react@1.4.35
1.5.14
Patch Changes
- Updated dependencies []:
- @executor-js/sdk@1.5.14
- @executor-js/config@1.5.14
- @executor-js/api@1.4.34
- @executor-js/react@1.4.34
1.5.13
Patch Changes
- Updated dependencies []:
- @executor-js/api@1.4.33
- @executor-js/react@1.4.33
- @executor-js/sdk@1.5.13
- @executor-js/config@1.5.13
1.5.12
Patch Changes
- Updated dependencies []:
- @executor-js/sdk@1.5.12
- @executor-js/config@1.5.12
- @executor-js/api@1.4.32
- @executor-js/react@1.4.32
1.5.11
Patch Changes
- Updated dependencies []:
- @executor-js/sdk@1.5.11
- @executor-js/config@1.5.11
- @executor-js/api@1.4.31
- @executor-js/react@1.4.31
1.5.10
Patch Changes
- Updated dependencies []:
- @executor-js/sdk@1.5.10
- @executor-js/config@1.5.10
- @executor-js/api@1.4.30
- @executor-js/react@1.4.30
1.5.9
Patch Changes
- Updated dependencies []:
- @executor-js/sdk@1.5.9
- @executor-js/config@1.5.9
- @executor-js/api@1.4.29
- @executor-js/react@1.4.29
1.5.8
Patch Changes
- Updated dependencies []:
- @executor-js/sdk@1.5.8
- @executor-js/config@1.5.8
- @executor-js/api@1.4.28
- @executor-js/react@1.4.28
1.5.7
Patch Changes
-
#964
7cee242Thanks @RhysSullivan! - Faster integrations with large API specsResolved OpenAPI spec text and GraphQL introspection snapshots are now stored content-addressed in the plugin blob store instead of inline in each integration's stored config. Listing integrations no longer loads multi-megabyte spec blobs it immediately discards, which makes the integrations surface dramatically faster for workspaces with large specs. Existing integrations keep working: rows that still inline a spec resolve unchanged and are rewritten in place the next time they are imported or refreshed.
-
Updated dependencies [
7cee242,7cee242]:- @executor-js/sdk@1.5.7
- @executor-js/api@1.4.27
- @executor-js/config@1.5.7
- @executor-js/react@1.4.27
1.5.4
Patch Changes
- Updated dependencies [
f485e4a]:- @executor-js/react@1.4.26
- @executor-js/sdk@1.5.4
- @executor-js/config@1.5.4
- @executor-js/api@1.4.26
1.5.3
Patch Changes
- Updated dependencies []:
- @executor-js/sdk@1.5.3
- @executor-js/config@1.5.3
- @executor-js/api@1.4.25
- @executor-js/react@1.4.25
1.5.2
Patch Changes
- Updated dependencies []:
- @executor-js/sdk@1.5.2
- @executor-js/config@1.5.2
- @executor-js/api@1.4.24
- @executor-js/react@1.4.24
1.5.1
Patch Changes
- Updated dependencies []:
- @executor-js/sdk@1.5.1
- @executor-js/config@1.5.1
- @executor-js/api@1.4.23
- @executor-js/react@1.4.23
1.5.0
Patch Changes
-
#922
1ba0193Thanks @RhysSullivan! - MoveeffectfromdependenciestopeerDependenciesin the published library packages so consumers provide a single shared Effect instance. -
#891
9c9bcb6Thanks @oscnord! - GraphQL sources now emit named operations (e.g.query Hello { ... }) instead of anonymous ones. This fixes invocation against servers that reject anonymous operations, and gives APM tooling that keys on the operation name a meaningful value. The operation name is derived from the root field name. -
Updated dependencies [
7d7fbbd,1ba0193]:- @executor-js/sdk@1.5.0
- @executor-js/config@1.5.0
- @executor-js/api@1.4.22
- @executor-js/react@1.4.22