MQTT Pub/Sub Explorer Tables #489
Open
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
…n/paima-engine into feature/events-and-primitives-explorer-tables
acedward
changed the title
|
In standby until MQTT is implemented |
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.
Disclaimer
This feature dependes on the following PRs:
#467
#471
#486
See the comparison between this and the latest branch in the series
Comparison
Features
The first table, "Tracked Contracts," displays a list of all the primitives that Paima Engine node is monitoring, showing the network type, a user-defined name for the primitive, the type of primitive, the contract address, and the block height. This feature leverages the existing /config API endpoint and required modifications to the frontend to fetch, process, and display this data in a new, dedicated table.
The second table, "Events," provides a real-time log of all the blockchain events that have been captured by the engine. This table shows the event name, the raw topic, the contract address from which the event was emitted, the event data, and the block number.
Added a new /events endpoint to the Paima Engine's API, which retrieves the event data from the database. This involved creating a new SQL query to fetch and paginate the events, updating the database layer to expose this query, and then modifying the frontend to call the new endpoint and display the data in its own table.