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: Fallback Sink #120

Merged
merged 3 commits into from
Apr 16, 2024
Merged

feat: Fallback Sink #120

merged 3 commits into from
Apr 16, 2024

Conversation

yhl25
Copy link
Contributor

@yhl25 yhl25 commented Apr 15, 2024

No description provided.

yhl25 added 3 commits April 14, 2024 15:37
Signed-off-by: Yashash H L <[email protected]>
Signed-off-by: Yashash H L <[email protected]>
Signed-off-by: Yashash H L <[email protected]>
@yhl25 yhl25 marked this pull request as ready for review April 15, 2024 15:28
@yhl25 yhl25 requested review from vigith and whynowy April 15, 2024 15:29
@vigith vigith merged commit 9747b4d into main Apr 16, 2024
3 checks passed
@vigith vigith deleted the fb-sink branch April 16, 2024 03:51
@@ -8,6 +8,8 @@ type Response struct {
Success bool `json:"success"`
// Err represents the error message when "success" is false.
Err string `json:"err,omitempty"`
// Fallback is true if the message to be sent to the fallback sink.
Fallback bool `json:"fallback,omitempty"`
Copy link
Member

Choose a reason for hiding this comment

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

Shall we combine Fallback and Success to use a new property?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I thought of using an enum, but enums might get tricky in some languages so went with two separate boolean values.

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.

3 participants