Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

[Notifier] [Bridge] Fix missed messageId for SendMessage object in slack notifier#40955

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Conversation

@WaylandAce
Copy link
Contributor

QA
Branch?5.2
Bug fix?yes
New feature?no
Deprecations?-
Tickets-
LicenseMIT
Doc PRsymfony/symfony-docs#...

There are missed messageId property for SendMessage object in slack notifier.
Regarding slack's documentation:https://api.slack.com/messaging/sending#publishing

One very important piece of information in this response is thets value, which is essentially the ID of the message,

@carsonbotcarsonbot added this to the5.2 milestoneApr 27, 2021
@WaylandAceWaylandAce changed the title[Notifier] [Bridge] Store message id for slack transport's SendMessage[Notifier] [Bridge] Fix missed messageId for SendMessage object in slack notifierApr 27, 2021
@WaylandAceWaylandAceforce-pushed thefeature/slack_bridge_notifier_message_id branch from3fae769 to374788dCompareApril 27, 2021 10:39

returnnewSentMessage($message, (string)$this);
$sentMessage =newSentMessage($message, (string)$this);
$sentMessage->setMessageId($result['ts']);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Shall we check if the key exists in the array?

Nyholm reacted with thumbs up emoji
Copy link
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

We already check for "ok" status. I had looked to another transports/bridges, they did not have even this checks.

Which behavior do you expect, if by some unknown reason slack return response with ok status, but with no messageid specified?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Yes, but ok let's keep it

@OskarStark
Copy link
Contributor

I would consider this a feature, it is working without the ID and must wait for5.4.

cc@nicolas-grekas

@WaylandAceWaylandAceforce-pushed thefeature/slack_bridge_notifier_message_id branch from374788d to838f36bCompareApril 27, 2021 17:17
@WaylandAce
Copy link
ContributorAuthor

I would consider this a feature, it is working without the ID and must wait for5.4.

cc@nicolas-grekas

I though to put this change as usual to 5.x branch, but checked "Maintenance" page (https://symfony.com/doc/current/contributing/code/maintenance.html) and it's sounds like it matches the rules.
Also 1 point to include this featurefix to nearest release, is the fact, that we cant fetch message id to reply/start thread in slack and this can be seen as problem.

Copy link
Member

@fabpotfabpot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

I'm fine merging it in 5.2.

OskarStark reacted with thumbs up emoji
@nicolas-grekas
Copy link
Member

Thank you@WaylandAce.

@nicolas-grekasnicolas-grekas merged commitd76bfb5 intosymfony:5.2May 7, 2021
This was referencedMay 9, 2021
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@fabpotfabpotfabpot approved these changes

@OskarStarkOskarStarkOskarStark approved these changes

Assignees

No one assigned

Projects

None yet

Milestone

5.2

Development

Successfully merging this pull request may close these issues.

5 participants

@WaylandAce@OskarStark@nicolas-grekas@fabpot@carsonbot

[8]ページ先頭

©2009-2025 Movatter.jp