Skip to content

Indexer chain name compatibility#2300

Open
fluidvanadium wants to merge 3 commits intodevfrom
get_lightd_info_compatibility
Open

Indexer chain name compatibility#2300
fluidvanadium wants to merge 3 commits intodevfrom
get_lightd_info_compatibility

Conversation

@fluidvanadium
Copy link
Copy Markdown
Contributor

Chaintype is now open to be inferred from Indexer.

use crate::config::{ChainType, ClientConfig};
use crate::config::ChainType;
use crate::config::ClientConfig;
use zingo_common_components::protocol::ActivationHeights;
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Is this the type we prefer for this?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

IDK, this PR didnt change that aspect, it only is imported here to complete a unit test.

/// Invalid chain type.
#[derive(thiserror::Error, Debug)]
#[error("Invalid chain type '{0}'. Expected one of: 'mainnet', 'testnet' or 'regtest'.")]
pub struct InvalidChainType(String);
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

i dont understand why this has moved in between the ChainType impls? please can we keep the impls together

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