Releases: seratch/slack-edge
version 1.3.5
Version 1.3.5 includes #48, a type export improvement contributed by @yinheli. Thank you so much for the contribution! All changes can be reviewed at 1.3.4...1.3.5
version 1.3.4
Version 1.3.4 resolves #46 bug in v1.3.3. If you're planning to use the newly added "authorizeErrorHandler" in your app, please upgrade to this version. Thank you so much @zhawtof for quickly reporting this issue! All changes can be reviewed at 1.3.3...1.3.4
version 1.3.3
Version 1.3.3 is now available with a new customize option called authorizeErrorHandler
!
If you want to ignore authorize errors for edge cases, which are not actionable for your app, you can set the following option to immediately return 200 OK / ack message in Socket Mode to Slack API servers.
const app = new SlackApp({
authorizeErrorHandler: async ({ request, error }) => new Response("", { status: 200 }),
// other arguments ...
});
All changes can be reviewed at 1.3.2...1.3.3
version 1.3.2
Version 1.3.2 is now available! Since this version, slack-edge supports "team" parameter for Slack app installation flow (OAuth). Thanks for the suggestion @zhawtof! All changes can be reviewed at 1.3.1...1.3.2
version 1.3.1
Version 1.3.1 is now available with some improvements contributed by @StephenTangCook. Thank you so much as always! All changes can be reviewed at 1.3.0...1.3.1
version 1.3.0
Version 1.3.0 is now available with several improvements. Notably, app.event
listeners now accept only publicly available, valid event names. While we consider it a minor breaking change, we believe it shouldn't affect any existing code that functions properly. All changes can be reviewed at 1.2.1...1.3.0
version 1.2.1
Version 1.2.1 improves missing properties in event payload data definition. All changes can be reviewed at 1.2.0...1.2.1
version 1.2.0
Version 1.2.0 improves the TypeScript types for app.action handlers. Here is a quick example demonstrating the new way to access channel-message/moda-view specific properties safely:
app.action<"button">("action_id", async ({ payload }) => {
// The payload can be either MessageBlockAction or ViewBlockAction here
// A few common properties are still accessible without if/else statements
const type: "block_actions" = payload.type;
const action: ButtonAction = payload.actions[0];
if ("message" in payload) {
// Within this clause, the properties that are only available
// when the action happens on a channel message are safely accessible.
const messageTs: string = payload.message.ts;
const channelId: string = payload.channel.id;
// for a workflow custom step, this has to be optional
const responseUrl: string | undefined = payload.response_url;
} else if ("view" in payload) {
// In the case of modal view or Home tab
}
});
Refer to #36 for more details.
All changes can be reviewed at 1.1.2...1.2.0
version 1.1.2
Version 1.1.2 enables developers to handle assistant app's bot user message events too. All changes can be reviewed at 1.1.1...1.1.2
version 1.1.1
Version 1.1.1 improves SlackOAuthApp to have more options for customizing it. All changes can be reviewed at 1.1.0...1.1.1