Type Checking Bug

[dave9123]

@slack/bolt version

4.4.0

Your App and Receiver Configuration

const app = new App({
    token: process.env.SLACK_OAUTH_TOKEN,
    signingSecret: process.env.SLACK_SIGNING_SECRET,
    socketMode: process.env.SLACK_SOCKET_MODE == "true",
    appToken: process.env.SLACK_SOCKET_MODE == "true" ? process.env.SLACK_APP_TOKEN : undefined,
    port: parseInt(process.env.SLACK_PORT || "3000", 10),
    customRoutes: [
        {
            path: "/ping",
            method: "GET",
            handler: (req, res) => {
                res.statusCode = 200;
                res.setHeader("Content-Type", "text/plain");
                res.end("Pong!");
            }
        }
    ]
});

Node.js runtime version

v22.17.0

Steps to reproduce:

tsconfig.json

{
    "compilerOptions": {
        "esModuleInterop": true,
        "skipLibCheck": true,
        "target": "es2022",
        "allowJs": true,
        "resolveJsonModule": true,
        "moduleDetection": "force",
        "isolatedModules": true,
        "strict": true,
        "noUncheckedIndexedAccess": true,
        "noImplicitOverride": true,
        "module": "NodeNext",
        "outDir": "dist",
        "sourceMap": true,
        "lib": [
            "es2022"
        ]
    },
    "include": [
        "src/**/*"
    ],
}

Steps to reproduce (this does not happens only on app.action)

1. On app.action, check body.user.username
2. On app.action, check body.actions[0].value
3. On app.action, check body.trigger_id

Expected result:

It shouldn't have show type errors

Actual result:

It seems to be showing up multiple errors on the type checking although it shows up when I try to view it through console.log

Errors

Property 'trigger_id' does not exist on type 'SlackViewAction'.\n Property 'trigger_id' does not exist on type 'ViewClosedAction'
Property 'username' does not exist on type '{ id: string; name: string; team_id?: string | undefined; } | { id: string; username: string; team_id?: string | undefined; } | { id: string; name?: string | undefined; username: string; team_id?: string | undefined; } | { ...; }'.\n Property 'username' does not exist on type '{ id: string; name: string; team_id?: string | undefined; }'
Property 'trigger_id' does not exist on type 'SlackAction'.\n Property 'trigger_id' does not exist on type 'DialogSubmitAction'
Property 'actions' does not exist on type 'SlackAction'.\n Property 'actions' does not exist on type 'DialogSubmitAction'
Property 'view' does not exist on type 'SlackAction'.\n Property 'view' does not exist on type 'InteractiveMessage'

[hello-ashleyintech]

hi, @dave9123! Thanks for submitting this.

Quick question before diving deeper - have you tried adding a type assertion for body, similar to in this issue here? let me know if this works for you - if not, I can dive deeper 😄

[dave9123]

Hey Ashley, here's the app.action with the type "block_actions" added, it still shows an error even after I've added it

{
    type: "section",
        text: {
        type: "mrkdwn",
            text: `Page ${page} of ${totalPages}`,
            },
},
{
    type: "actions",
        elements: [
            {
                type: "button",
                text: {
                    type: "plain_text",
                    text: "Previous"
                },
                action_id: "previous_page",
                value: (page - 1).toString(),
            },
            {
                type: "button",
                text: {
                    type: "plain_text",
                    text: "Next"
                },
                action_id: "next_page",
                value: (page + 1).toString(),
            }
        ]
}

[github-actions]

👋 It looks like this issue has been open for 30 days with no activity. We'll mark this as stale for now, and wait 10 days for an update or for further comment before closing this issue out. If you think this issue needs to be prioritized, please comment to get the thread going again! Maintainers also review issues marked as stale on a regular basis and comment or adjust status if the issue needs to be reprioritized.

[dave9123]

Will this be fixed soon?