Generated endpoint markers and devdock examples#45
Draft
kvz wants to merge 20 commits into
Draft
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #45 +/- ##
===========================================
- Coverage 82.60% 67.88% -14.73%
===========================================
Files 6 6
Lines 345 439 +94
===========================================
+ Hits 285 298 +13
- Misses 32 112 +80
- Partials 28 29 +1 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This was referenced May 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Experimental Status
Experimental work: this PR is part of the API2 contract/generated SDK effort and is intentionally kept as a Draft while the generated surface is validated.
Why
API2 is becoming the source of truth for endpoint contracts and SDK generation. This Go SDK companion proves two things cautiously: API2 can delete/rewrite generated Go regions without behavior drift, and checked-in Go examples can exercise that generated surface against devdock as normal consumer code.
What changed
Client.CreateTusAssembly()andClient.WaitForAssembly()coverage through API2's generator.AssemblyInfo/FileInfofields that the contract says SDK examples need.examples/api2-devdock-tus-assembly/main.go.scenario.preparations[]feature-call input forcreateTusAssemblyinstead of the temporaryscenario.createTusAssemblycompatibility field.Verification
api2/bin/cli.ts contracts sdks --no-motd --target transloadit --platform go --sdk-root ../go-sdk --rewrite-sdk --compare-existingcore/bin/devdock.ts exec tstrun system/sdk_examples/go-transloadit-examples.test.ts -vv --max-time-per-test 420go test ./examples/api2-devdock-tus-assembly ./examples/api2-devdock-template-lifecyclego test ./... -run 'Test(NewClient|FormFieldValue|AssemblyInfo_TusFields)'Notes
Full
go test ./...still expects liveTRANSLOADIT_KEY/TRANSLOADIT_SECRETfor integration-style tests. I left those untouched and ran the credential-free subset plus API2's devdock system example lane.Companion PRs
Transloadit
TUS
Allowed outward links from Transloadit to the related tus companion PRs: