Skip to content

Conversation

SupernaviX
Copy link
Collaborator

WIP

@SupernaviX SupernaviX mentioned this pull request Sep 2, 2025
@alexwoods alexwoods requested a review from sandtreader October 15, 2025 18:19
@sandtreader sandtreader marked this pull request as ready for review October 16, 2025 13:19
Copy link
Collaborator

@sandtreader sandtreader left a comment

Choose a reason for hiding this comment

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

Great work - comments are primarily about code location

pallas-addresses = "0.33.0"
pallas-crypto = "0.33.0"
pallas-primitives = "0.33.0"
pallas-traverse = "0.33.0"
Copy link
Collaborator

Choose a reason for hiding this comment

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

Only just noticed these were already workspace dependencies on Pallas... Can we avoid this? I was hoping if we didn't expose Pallas in any common/ interfaces we could protect modules from this dependency unless they absolutely need it.

RolledBack, // Volatile, restarted after rollback
}

macro_rules! declare_byte_array_type {
Copy link
Collaborator

Choose a reason for hiding this comment

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

Think this should be split out, as discussed generally


macro_rules! declare_byte_array_type_with_bech32 {
($name:ident, $size:expr, $hrp:expr) => {
declare_byte_array_type!($name, $size);
Copy link
Collaborator

Choose a reason for hiding this comment

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

Yay, inheritance in Rust ;-)

}

/// Handle `/blocks/latest`, `/blocks/{hash_or_number}`
pub async fn handle_blocks_latest_hash_number_blockfrost(
Copy link
Collaborator

Choose a reason for hiding this comment

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

Given this is in a rest_blockfrost module, do we need all these _blockfrost suffixes?

Copy link
Collaborator

Choose a reason for hiding this comment

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

I don't think we do, but I was maintaining consistency with the other functions in the crate

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