Skip to content

Support encoding comments by exposing the type#48

Open
dprotaso wants to merge 3 commits into
launchdarkly:mainfrom
dprotaso:support-encoding-comments
Open

Support encoding comments by exposing the type#48
dprotaso wants to merge 3 commits into
launchdarkly:mainfrom
dprotaso:support-encoding-comments

Conversation

@dprotaso

@dprotaso dprotaso commented May 14, 2025

Copy link
Copy Markdown

Prior to this it was not possible to encode comments using the
encoder

@dprotaso dprotaso requested a review from a team as a code owner May 14, 2025 22:36
Comment thread server.go Outdated

@keelerm84 keelerm84 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I'm not sure I understand the need for this change.

Prior to this it was not possible to publish comments using the encoder

The encoder doesn't publish comments. It encodes them.

The server can publish messages though. And you can publish a comment with it using the PublishComment method.

@keelerm84 keelerm84 added the waiting for feedback Indicates LaunchDarkly is waiting for customer feedback before issue is closed due to staleness. label May 19, 2025
@dprotaso

dprotaso commented May 19, 2025

Copy link
Copy Markdown
Author

I'm not sure I understand the need for this change.

I'm using your encoder but not your server.

The encoder doesn't publish comments. It encodes them.

Sorry that was a typo and should say 'encode comments' - updated

@dprotaso

Copy link
Copy Markdown
Author

Hey any updates?

@dprotaso

Copy link
Copy Markdown
Author

@keelerm84 any update?

Prior to this it was not possible to publish comments using the
encoder
@dprotaso dprotaso force-pushed the support-encoding-comments branch from 59012e0 to b5b7b03 Compare August 14, 2025 14:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

waiting for feedback Indicates LaunchDarkly is waiting for customer feedback before issue is closed due to staleness.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants