Skip to content

Add Slack message reference parsing utilities#1518

Closed
Cr1stal wants to merge 1 commit into
slackapi:mainfrom
Cr1stal:feature/parse-slack-message-references
Closed

Add Slack message reference parsing utilities#1518
Cr1stal wants to merge 1 commit into
slackapi:mainfrom
Cr1stal:feature/parse-slack-message-references

Conversation

@Cr1stal
Copy link
Copy Markdown

@Cr1stal Cr1stal commented May 31, 2026

Summary

Adds syntax-only parsing utilities for Slack message references.

Related to #1108.

  • Add slack_bolt.message_references for parsing mrkdwn references in message text
  • Support user, channel, user group, special mention, date, link, and unknown references
  • Add tests for labeled/unlabeled references, unknown references, date links, and escaped or multiline angle brackets
  • Document parse_slack_references() in the message-listening guide

Testing

  • ./scripts/install_all_and_run_tests.sh
  • ./scripts/format.sh --no-install
  • ./scripts/lint.sh --no-install
  • ./scripts/run_tests.sh tests/slack_bolt/test_message_references.py tests/slack_bolt/util/test_util.py
  • ./scripts/run_mypy.sh --no-install
  • git diff --check

Category

  • slack_bolt.App and/or its core components
  • slack_bolt.async_app.AsyncApp and/or its core components
  • Adapters in slack_bolt.adapter
  • Document pages under /docs
  • Others

Requirements

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

  • I've read and understood the Contributing Guidelines and have done my best effort to follow them.
  • I've read and agree to the Code of Conduct.
  • I've run ./scripts/install_all_and_run_tests.sh after making the changes.

@Cr1stal Cr1stal marked this pull request as ready for review May 31, 2026 05:32
@Cr1stal Cr1stal requested review from a team as code owners May 31, 2026 05:32
@WilliamBergamin
Copy link
Copy Markdown
Contributor

Hi @Cr1stal thanks for your interest in our project 💯

As mentioned in #1518 we don't have immediate plans to add this feature, this also involves maintaining and ensure its quality over time and as the project evolves, for this reason I've decided to close this PR

If we commit to introducing this feature we can always revisit/reopen these changes 🙏

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants