Skip to content

refactor(adapters/slack): move remaining adapter calls onto typed slackapi methods #100

Open

Description

@ThomasK33

Follow-up from #97. The Slack adapter now uses slackapi for transport, retry, signature checks, and history reads. It still builds its own request bodies for four methods:

  • auth.test
  • chat.postMessage
  • chat.postEphemeral
  • conversations.open

Move these onto the typed slackapi methods so the adapter has one request encoding per method. The existing adapter hardening tests are the acceptance bar: they must keep passing without being weakened.


Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: medium

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    ready-for-agentFully specified, ready for an AFK agent

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions