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

Make sure the export package is visitable #172

Merged
merged 2 commits into from
Aug 16, 2024
Merged

Conversation

Sushisource
Copy link
Member

Go version auto-updated itself, seemingly because of dependencies.

What changed?
Add the top level type of the export package to the visit walking mechanics

Why?
So users can visit payloads on these types

How did you test it?
Upgraded test

Potential risks
Nada

Closes temporalio/sdk-go#1566

@Sushisource Sushisource requested review from a team as code owners August 16, 2024 21:35
Comment on lines 30 to 31
"go.temporal.io/api/export/v1"
"go.temporal.io/api/history/v1"
Copy link
Member

Choose a reason for hiding this comment

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

Go fmt I would expect would fix this to move non-stdlib imports to later, but no biggie

@Sushisource Sushisource enabled auto-merge (squash) August 16, 2024 23:08
@Sushisource Sushisource merged commit d2920d1 into master Aug 16, 2024
3 checks passed
@Sushisource Sushisource deleted the add-export-to-visi branch August 16, 2024 23:08
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.

go.temporal.io/api/proxy.VisitPayloads doesn't visit export package
2 participants