Skip to content

feat: add webapi response changes as of 2026-11-17 - #1636

Open
slackapi[bot] wants to merge 267 commits into
mainfrom
api
Open

slackapi[bot] wants to merge 267 commits into
mainfrom
api

Conversation

@slackapi

@slackapi slackapi Bot commented Aug 22, 2026

Copy link
Copy Markdown
Contributor

This PR updates the web API client and model based on the production E2E test results.

Category

  • slack-api-model (Slack API Data Models)

Requirements

Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you agree to those rules.

@slackapi
slackapi Bot requested a review from a team as a code owner August 22, 2026 00:54
@slackapi slackapi Bot added project:slack-api-model project:slack-api-model semver:patch labels Aug 22, 2026
@codecov

codecov Bot commented Aug 22, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 73.91%. Comparing base (ba1aa12) to head (b796e10).
⚠️ Report is 1 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files
@@             Coverage Diff              @@
##               main    #1636      +/-   ##
============================================
+ Coverage     73.82%   73.91%   +0.08%     
- Complexity     4782     4797      +15     
============================================
  Files           489      489              
  Lines         14920    14959      +39     
  Branches       1559     1562       +3     
============================================
+ Hits          11015    11057      +42     
+ Misses         2978     2977       -1     
+ Partials        927      925       -2     
Flag Coverage Δ
jdk-14 73.91% <ø> (+0.08%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

@zimeg

zimeg commented Aug 25, 2026

Copy link
Copy Markdown
Member

⚠️ EXPERIMENTAL — Slack Lists message field re-typed as List<MessageRef> (388afd370)

Pushed an experimental change to how ListRecord.Field.message is modeled. Not final — do not merge as-is. Flagging it here with full context for review.

What changed

ListRecord.Field.message is now List<ListRecord.MessageRef> where MessageRef = { value, channel_id, ts, thread_ts? }. The prior Message-typed modeling (#1590) is replaced; the test-tree GsonListRecordFieldFactory is reduced to a pass-through and its tests rewritten against the new shape.

Why — verified against the live API

The response shape was confirmed empirically on two surfaces, across single/threaded/multi-reference scenarios:

Both return the message field as [{ "value": "<permalink>", "channel_id": "C…", "ts": "…", "thread_ts"?: "…" }] — always an array, with thread_ts present only when the referenced message is a threaded reply. No single-object form was observed on either endpoint. Element is a message reference, not a chat message. Field-type reference: slackLists.items.create#field-types.

This means the earlier Message element type did not match the payload, and the single-object↔array normalization added in #1590 handled a shape the API does not actually return on these endpoints.

Open question (the reason this is experimental)

This fixes the response only. The request side of the field takes an array of permalink URL strings (List<String>) — verified: the API rejects object form with must provide a string [json-pointer:/initial_fields/0/message/0]. A single Field.message type cannot serve both directions. The request/response split still needs a design decision (direction-aware types, or bring Lists types under codegen). This is the same request-vs-response tension previously seen on the Node side.

Related / for later reference

  • #1590 — the earlier Java array-deserialization fix (runtime crash) that this supersedes on the model side.
  • java-slack-sdk ListRecord.Field.message` deserialization fails when Slack returns an array #1587 — the runtime JsonSyntaxException on array-shaped message; fixed (that was a crash; distinct from this typing question).
  • node-slack-sdk #2598 — the analogous Node bug: the generated response type is wrong for this field. This model fix is the upstream half of resolving it (Node response types generate from Java samples).
  • node-slack-sdk #2599 / #2600 — hand-split attempts at #2598 that modeled Message | Message[]; obsolete — they used the wrong element type and an unnecessary union (the field is array-only, and the element is a reference, not a Message).

Verification was done against a test workspace; a few throwaway probe lists (clack probe …) were created there and can be cleaned up.

zimeg and others added 25 commits August 25, 2026 14:55
An ad-hoc runner run merged a full rich Message object into the
response_metadata.messages field of every slackLists.* sample (~516 lines
each: attachments, bot_profile, wibblr, nested recursion). That field on a
slackLists response carries warning strings, not a chat message — the content
is bogus and broke PR #1636's diff. Restore all 10 slackLists samples to their
main-branch state (clean, empty response_metadata.messages).

Co-Authored-By: Claude <svc-devxp-claude@slack-corp.com>
…_denied audit action

❤️
Co-Authored-By: Claude <svc-devxp-claude@slack-corp.com>
…ction

❤️
Co-Authored-By: Claude <svc-devxp-claude@slack-corp.com>
…ect)

The live API returns ai_summary as an object when populated but an empty
string when absent, so the earlier String typing failed with
"Expected STRING but was BEGIN_OBJECT at path $.ai_summary". Object
tolerates both shapes.

❤️
Co-Authored-By: Claude <svc-devxp-claude@slack-corp.com>
Replaces the Object stopgap. Verified against a live files.info call:
ai_summary is a structured object {id, unfurl_enabled, status, content},
or omitted when absent — the live API never returns the empty-string form
(that only appears in generated sample fixtures, which no test parses into
a File), so no custom deserializer is needed: Gson maps omitted -> null and
the object -> AiSummary natively.

❤️
Co-Authored-By: Claude <svc-devxp-claude@slack-corp.com>
…amily

The audit test getActions_detectingNewOnes checks each live action against
the SDK constants in its matching category class. team_ip_allowlist_range_added
was mistakenly placed in Actions.User (next to team_ip_allowlist_access_denied),
but the raw audit actions fixture categorizes it under workspace_or_org, so the
WorkspaceOrOrg check failed. Moved it there and added the rest of the family the
fixture lists (range_removed, enabled, disabled) to pre-empt the same red on
subsequent runs. team_ip_allowlist_access_denied correctly stays in User (the
fixture lists it under /actions/user).

❤️
Co-Authored-By: Claude <svc-devxp-claude@slack-corp.com>
❤️
Co-Authored-By: Claude <svc-devxp-claude@slack-corp.com>
❤️
Co-Authored-By: Claude <svc-devxp-claude@slack-corp.com>
Add the pref.alt_text_reminders action constant to Actions.WorkspaceOrOrg
and a typed condition field (AAARuleCondition) to LogsResponse.Details for
the app_allowlist_rule_* actions.

❤️
Co-Authored-By: Claude <svc-devxp-claude@slack-corp.com>
Add the pref.canvas_printing_enabled action constant to
Actions.WorkspaceOrOrg and a Boolean is_enabled field to
LogsResponse.Details.

❤️
Co-Authored-By: Claude <svc-devxp-claude@slack-corp.com>
zimeg and others added 3 commits November 16, 2026 17:48
… samples

The label map is keyed by each input's value, so the generator kept live values as keys after masking every value.

Co-Authored-By: Claude <svc-devxp-claude@slack-corp.com>
Co-Authored-By: Claude <svc-devxp-claude@slack-corp.com>
…ed_fields

Co-Authored-By: Claude <svc-devxp-claude@slack-corp.com>
@zimeg zimeg added the project:slack-api-client project:slack-api-client label Nov 17, 2026
@zimeg zimeg self-assigned this Nov 17, 2026
@zimeg zimeg added this to the 1.55.1 milestone Nov 17, 2026
@zimeg zimeg changed the title feat: add webapi response changes as of 2026-08-22 feat: add webapi response changes as of 2026-11-17 Nov 17, 2026
zimeg and others added 3 commits November 16, 2026 18:42
❤️
Co-Authored-By: Claude <svc-devxp-claude@slack-corp.com>
Co-Authored-By: Claude <svc-devxp-claude@slack-corp.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude <svc-devxp-claude@slack-corp.com>
@zimeg
zimeg changed the base branch from main to details-action November 17, 2026 02:49
zimeg and others added 9 commits November 16, 2026 20:06
Five samples on this branch lost properties that main still has, including deprecated_argument and message.assistant_app_thread in chat.postMessage and most files.matches[] fields in search.all. Each sample is now the union of both, and no existing value changed.

Co-Authored-By: Claude <svc-devxp-claude@slack-corp.com>
… list pins, native dlp admin notification frequency and slackbot ai mcp server instructions actions to Actions

❤️
Co-Authored-By: Claude <svc-devxp-claude@slack-corp.com>
…ains

Co-Authored-By: Claude <svc-devxp-claude@slack-corp.com>
Co-Authored-By: Claude <svc-devxp-claude@slack-corp.com>
Co-authored-by: Cheng Chen <35309699+cchensh@users.noreply.github.com>

Co-Authored-By: Claude <svc-devxp-claude@slack-corp.com>
Co-Authored-By: Claude <svc-devxp-claude@slack-corp.com>
@zimeg
zimeg changed the base branch from details-action to main November 18, 2026 21:57
zimeg and others added 7 commits November 18, 2026 13:58
Co-Authored-By: Claude <svc-devxp-claude@slack-corp.com>
…box, search developer samples, slackbot feedback and traces listed actions to Actions

❤️
Co-Authored-By: Claude <svc-devxp-claude@slack-corp.com>
The function_inputs map is keyed by each workflow's input names, so the generator now keeps one string input and one credential input under placeholder keys.

Co-Authored-By: Claude <svc-devxp-claude@slack-corp.com>
Co-Authored-By: Claude <svc-devxp-claude@slack-corp.com>
…mples

Co-Authored-By: Claude <svc-devxp-claude@slack-corp.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

project:slack-api-client project:slack-api-client project:slack-api-model project:slack-api-model semver:patch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant