refactor: lay the tree out by mechanism role - #2
Merged
Conversation
The top level is the x402 role grid: facilitator/ verify, settle, and the facilitator service server/exact/ the SchemeNetworkServer a seller mounts (package exact) client/ the SchemeNetworkClient, sources in src/, emit in dist/ cmd/ examples/ e2e/ Import paths lose the go/ segment: x402/go/facilitator → x402/facilitator x402/go/mechanisms/gno/exact/server → x402/server/exact x402/go/e2e → x402/e2e The scheme keeps a segment of its own because a second scheme would need one; the namespace does not, since every mechanism here is gno. The JS buyer lives with the test that drives it, as e2e/buyer.mjs beside pay_test.go. It imports the mechanism by package name, so the exports map stays covered. gofmt runs over . rather than a named tree. e2e remains its own module, so `go test ./...` cannot start a chain.
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.
The top level is the x402 role grid:
facilitator/ verify, settle, and the facilitator service
server/exact/ the SchemeNetworkServer a seller mounts (package exact)
client/ the SchemeNetworkClient, sources in src/, emit in dist/
cmd/ examples/ e2e/
Import paths lose the go/ segment:
x402/go/facilitator → x402/facilitator
x402/go/mechanisms/gno/exact/server → x402/server/exact
x402/go/e2e → x402/e2e
The scheme keeps a segment of its own because a second scheme would need
one; the namespace does not, since every mechanism here is gno.
The JS buyer lives with the test that drives it, as e2e/buyer.mjs beside
pay_test.go. It imports the mechanism by package name, so the exports map
stays covered.
gofmt runs over . rather than a named tree. e2e remains its own module, so
go test ./...cannot start a chain.