Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

verkle: extract static constructor #3616

Merged
merged 3 commits into from
Aug 29, 2024
Merged

verkle: extract static constructor #3616

merged 3 commits into from
Aug 29, 2024

Conversation

ScottyPoi
Copy link
Contributor

ref issue: #3560

VerkleTree:
moves state VerkleTree.create to 'constructors.ts'
renames it to createVerkleTree

Copy link
Contributor

@acolytec3 acolytec3 left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link

codecov bot commented Aug 29, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 31.33%. Comparing base (4470cc3) to head (7d9a611).
Report is 25 commits behind head on master.

Additional details and impacted files

Impacted file tree graph

Flag Coverage Δ
block 66.31% <ø> (-7.14%) ⬇️
blockchain 84.92% <ø> (?)
client ?
common 89.68% <ø> (?)
devp2p 0.00% <ø> (?)
genesis 0.00% <ø> (?)
statemanager 66.17% <ø> (?)
trie 52.05% <ø> (?)
tx ?
util 70.20% <ø> (?)
wallet ?

Flags with carried forward coverage won't be shown. Click here to find out more.

@acolytec3 acolytec3 merged commit 0cf6399 into master Aug 29, 2024
38 checks passed
@ScottyPoi ScottyPoi deleted the verkle-constructor branch August 29, 2024 17:19
@@ -24,6 +21,8 @@ import {
type VerkleTreeOptsWithDefaults,
} from './types.js'

// eslint-disable-next-line @typescript-eslint/no-unused-vars
import type { createVerkleTree } from './constructors.js' // Imported so intellisense can display docs
Copy link
Member

Choose a reason for hiding this comment

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

Ah, yeah, I stumbled over this as well at some point. It would really be good if this can be solved on a more global scale (all such imports auto-added or so), this problem is all over the place and it would be good if we could use this @link feature from the docs more reliably.

(just as some PR-unrelated side note)

Copy link
Contributor

@acolytec3 acolytec3 Sep 2, 2024

Choose a reason for hiding this comment

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

Yup, have done some research on this but haven't quite solved it yet. We need to somehow link via something like {@link module#referencedType } but I haven't figured out specifically how to implement yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants