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

feat: adding destination id #9

Merged
merged 1 commit into from
Apr 22, 2024
Merged

Conversation

achettyiitr
Copy link
Member

Description

  • Adding destinationID to message properties. This is being used for retl events.

Linear Ticket

  • Resolves PIPE-1026

Security

  • The code changed/added as part of this pull request won't create any security issues with how the software is being used.

@achettyiitr achettyiitr enabled auto-merge (squash) April 22, 2024 17:53
Copy link
Contributor

@mihir20 mihir20 left a comment

Choose a reason for hiding this comment

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

LGTM

@achettyiitr achettyiitr merged commit ee57769 into main Apr 22, 2024
6 checks passed
@achettyiitr achettyiitr deleted the feat.addiding-destination-id branch April 22, 2024 17:54
@@ -33,6 +34,7 @@ type MessageProperties struct {
SourceID string `json:"sourceID" validate:"required"`
ReceivedAt time.Time `json:"receivedAt" validate:"required"`
RequestIP string `json:"requestIP" validate:"required"`
DestinationID string `json:"destinationID"` // optional
Copy link
Collaborator

Choose a reason for hiding this comment

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

@achettyiitr We could have had omitempty here as well like for the other optional parameters, right?

Copy link
Member Author

Choose a reason for hiding this comment

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

Sorry, missed this comment. Adding it in a separate PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants