Skip to content

Comments

chore: move init_defaults to tempo-node crate for easier re-use in other binaries#2782

Open
zerosnacks wants to merge 3 commits intomainfrom
move-init-defaults-to-node
Open

chore: move init_defaults to tempo-node crate for easier re-use in other binaries#2782
zerosnacks wants to merge 3 commits intomainfrom
move-init-defaults-to-node

Conversation

@zerosnacks
Copy link
Contributor

Move init_download_urls, init_payload_builder_defaults, init_txpool_defaults and the public init_defaults function from bin/tempo into crates/node/src/defaults.rs.

Re-export init_defaults from tempo_node lib.rs alongside init_version_metadata.

Telemetry CLI types (TelemetryArgs, UrlWithAuth, TelemetryConfig) remain in the tempo binary as they are CLI-specific.

Move init_download_urls, init_payload_builder_defaults, init_txpool_defaults
and the public init_defaults function from bin/tempo into crates/node/src/defaults.rs.

Re-export init_defaults from tempo_node lib.rs alongside init_version_metadata.

Telemetry CLI types (TelemetryArgs, UrlWithAuth, TelemetryConfig) remain in
the tempo binary as they are CLI-specific.

Amp-Thread-ID: https://ampcode.com/threads/T-019c76ac-cb19-70fd-aa37-75be4e69ea25
Co-authored-by: Amp <amp@ampcode.com>
@zerosnacks zerosnacks changed the title move init_defaults to tempo-node crate chore: move init_defaults to tempo-node crate for easier re-use in other binaries Feb 19, 2026
Copy link
Contributor

@0xrusowsky 0xrusowsky left a comment

Choose a reason for hiding this comment

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

i don't see any problem with this, but let's wait for more reviewers

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.

2 participants