-
Notifications
You must be signed in to change notification settings - Fork 84
Feat/add tx codec 20250822 #27
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
Closed
JamesPiechota
wants to merge
2,506
commits into
samcamwilliams:main
from
permaweb:feat/add-tx-codec-20250822
Closed
Feat/add tx codec 20250822 #27
JamesPiechota
wants to merge
2,506
commits into
samcamwilliams:main
from
permaweb:feat/add-tx-codec-20250822
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit adds the `[email protected]` device, allowing for key and value searches for messages across HyperBEAM stores using a simple AO-Core HTTP interface. As the moduledoc describes, the interface is as follows: ``` A discovery engine for searching for and returning messages found in a node's cache, through supported stores. This device supports various modes of matching, including: - `all' (default): Match all keys in the request message. - `base': Match all keys in the base message. - `only': Match only the key(s) specified in the `only' key. The `only' key can be a binary, a map, or a list of keys. If it is a binary, it is split on commas to get a list of keys to search for. If it is a message, it is used directly as the match spec. If it is a list, it is assumed to be a list of keys that we should select from the request or base message and use as the match spec. The `return' key can be used to specify the type of data to return. - `count': Return the number of matches. - `paths': Return the paths of the matches in a list. - `messages': Return the messages associated with each match in a list. - `first-path': Return the first path of the matches. - `first-message': Return the first message of the matches. - `boolean': Return a boolean indicating whether any matches were found. ``` Presently, only the LMDB store (HyperBEAM's default) offers the necessary querying engine. This feature is intended as a baseline for future work that offers full support for Arweave and AO GraphQL-based search.
feat: Rich querying of HyperBEAM stores
impr: `[email protected]` improvements, fixing `committed` key generation
feat: `[email protected]` deep path evaluation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.