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

fix: ensure targets are propagated to inbox#16985

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

Merged
DanielleMaywood merged 1 commit intomainfromdm-bugfix-inbox-targets
Mar 19, 2025

Conversation

DanielleMaywood
Copy link
Contributor

@DanielleMaywoodDanielleMaywood commentedMar 18, 2025
edited
Loading

Currently thetargets column ininbox_notifications doesn't get filled. This PR fixes that. Rather than give targets special treatment, we should put it in the payload like everything else. This correctly propagates notification targets to the inbox table without much code change.

Rather than give targets special treatment, we should put it in thepayload like everything else. This correctly propagates notificationtargets to the inbox table without much code change.
@DanielleMaywoodDanielleMaywood changed the titlebugfix: ensure targets are propagated to inboxfix: ensure targets are propagated to inboxMar 18, 2025
@DanielleMaywoodDanielleMaywood marked this pull request as ready for reviewMarch 18, 2025 16:28
@DanielleMaywoodDanielleMaywood requested review fromdefelmnq andmtojek and removed request fordefelmnqMarch 18, 2025 16:40
@@ -74,7 +74,7 @@ func (s *StoreEnqueuer) EnqueueWithData(ctx context.Context, userID, templateID
dispatchMethod = metadata.CustomMethod.NotificationMethod
}

payload, err := s.buildPayload(metadata, labels, data)
payload, err := s.buildPayload(metadata, labels, data, targets)
Copy link
Member

Choose a reason for hiding this comment

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

Is it the first time we're processing targets? Before we merge this one, I'd like to understand the use case. AFAIRtargets is an array of UUIDs, and that can be a combination of user UUID, template UUID, workspace UUID. Are we going to discover types of resources?

Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

So@defelmnq's PR#16764 already updated theMessagePayload datatype to includeTargets. The PR didn't fill our theTargets field though, so I'm assuming that was missed and this was the intended approach.

Copy link
Member

Choose a reason for hiding this comment

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

I see, I missed the context. Obviously it is too late for this feedback, so ignore the comment 👍

Copy link
Member

@mtojekmtojek left a comment

Choose a reason for hiding this comment

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

LGTM 👍

@DanielleMaywoodDanielleMaywood merged commitef62e62 intomainMar 19, 2025
38 checks passed
@DanielleMaywoodDanielleMaywood deleted the dm-bugfix-inbox-targets branchMarch 19, 2025 09:51
@github-actionsgithub-actionsbot locked and limited conversation to collaboratorsMar 19, 2025
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.
Reviewers

@mtojekmtojekmtojek approved these changes

@defelmnqdefelmnqAwaiting requested review from defelmnq

Assignees

@DanielleMaywoodDanielleMaywood

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

2 participants
@DanielleMaywood@mtojek

[8]ページ先頭

©2009-2025 Movatter.jp