Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PinnedMessageItem interface missing ts #2163

Closed
maxretries opened this issue Jul 12, 2024 · 1 comment · Fixed by #2164
Closed

PinnedMessageItem interface missing ts #2163

maxretries opened this issue Jul 12, 2024 · 1 comment · Fixed by #2164
Labels
bug M-T: confirmed bug report. Issues are confirmed when the reproduction steps are documented enhancement M-T: A feature request for new functionality semver:minor TypeScript-specific
Milestone

Comments

@maxretries
Copy link
Contributor

@slack/bolt version

3.19.0

Your App and Receiver Configuration

Not applicable, issue with types

Node.js runtime version

Not applicable, issue with types

Steps to reproduce:

pin_added and pin_removed event send the ts of the pinned message. However this is missing in the PinnedMessageItem

Expected result:

ts should be part of PinnedMessageItem interface.

Actual result:

ts is currently not defined in PinnedMessageItem interface

@filmaj filmaj added this to the 3.20.0 milestone Jul 12, 2024
@filmaj filmaj added bug M-T: confirmed bug report. Issues are confirmed when the reproduction steps are documented enhancement M-T: A feature request for new functionality semver:minor TypeScript-specific and removed untriaged labels Jul 12, 2024
@filmaj
Copy link
Contributor

filmaj commented Jul 12, 2024

Good catch! Thanks for filing. Confirmed in my local testing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug M-T: confirmed bug report. Issues are confirmed when the reproduction steps are documented enhancement M-T: A feature request for new functionality semver:minor TypeScript-specific
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants