Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
In the new multi-format ssb-ebt we need to be able to get any feedID and infer what is it: is it a classic
main
feed? Is it aclassic
index feed? Is it a bendy butt? (The first 2 questions are the most important) It's not enough to just look at the feedId and infer thefeedformat
, we also need to know thefeedpurpose
. In ssb-replication-scheduler we will also need something like this.Solution
New API
findById()
. Turns out it was already implemented asgetMetadata
, I just did further tweaking in its internals, to:findById()
has been tombstoned, returnnull
feedformat
from thefeedId
type
andnonce
etcmsg.value.content
undermetadata
object, like it is during subfeed creation