-
Notifications
You must be signed in to change notification settings - Fork 132
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
Add tracking tips explorer multiverse #2981
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. The tests are passing on my machine. Please resolve the linter warnings. They are preventing the project from being compiled due to -D warnings
.
display("the explorer's database couldn't be initialized: {}", msg) | ||
} | ||
} | ||
#[derive(Debug, Error)] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Woohoo, removing last error_chain
pieces!
038a68b
to
f985ae4
Compare
although unlikely, it may report false positives otherwise also, it's probably a bit more efficient
The nightly failure is resolved in #2995. |
Intermediate step, see #2963
This essentially changes the explorer backend/indexing, but without adding the breaking changes to graphql.
This may conflict with #2962, it's not really dependent, but it touches the same things. I would merge #2962 first anyway, so maybe I'll rebase this one on top.
Backend
State
, so theExplorerDB
can be used likeget_branch(hash)
orget_main_branch(hash)
. Also, change the graphql queries so they useget_main_branch
, so this PR still retains most of the current behaviour.GraphQL API
The changes to the
graphql/mod.rs
are only to make things still compile, most queries keep the current behavior except forbreaking changes will come in the next PR.