Skip to content

Conversation

cedric-cordenier
Copy link
Contributor

Requires

Supports

Copy link

github-actions bot commented Oct 9, 2025

👋 cedric-cordenier, thanks for creating this pull request!

To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team.

Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks!

Copy link

github-actions bot commented Oct 9, 2025

✅ API Diff Results - No breaking changes


📄 View full apidiff report | 📚 Learn about apidiff

},
},
})
require.Equal(t, "Bar", result.GetValue().GetStringValue(), result.GetError())
Copy link
Contributor

Choose a reason for hiding this comment

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

maybe missing some parent test context, but where does the value "Bar" come from if this is expected to error?

require.Equal(t, "Bar", result.GetValue().GetStringValue())
})

t.Run("returns an error when there are invalid UTF-8 bytes", func(t *testing.T) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Can you also add one that shows the SDK returns the right error from the host?

require.Equal(t, "Bar", result.GetValue().GetStringValue())
})

t.Run("returns an error when there are invalid UTF-8 bytes", func(t *testing.T) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Tests fail because you didn't implement the STD test for common. This version of it verifies the test can pass. Once you have that, I would implement it in Go's SDK too to ensure assumptions you made are correct about messaging (eg the bar question that Street asked below).

It sucks, but it keeps us from having a circular dependency. I think of Go as the reference implementation, even though it's not with the host, it's good to ensure it passes.

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