feat: implement data reception layer with WebSocket and HTTP support#27
Merged
FabianSanchezD merged 2 commits intoNeko-Protocol:mainfrom Jan 31, 2026
Merged
Conversation
Contributor
Author
|
Hi @FabianSanchezD Could you please review my issue? |
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
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.
🚀 Neko Pull Request
Mark with an
xall the checkboxes that apply (like[x])📌 Type of Change
📝 Changes description
Implemented the Data Reception Layer for the Aggregator service, enabling efficient communication with the Ingestor service.
Key Features:
class-validatorandclass-transformerto ensure the integrity of incoming messages (DTOs).price.received) usingEventEmitter2for asynchronous processing.📸 Evidence (A Loom/Cap video is required as evidence, we WON'T merge if there's no proof)
Test Execution Results:
⏰ Time spent breakdown
🌌 Comments
The service is designed to be resilient to network failures thanks to the reconnection logic. NestJS best practices were followed, utilizing dependency injection and decorators throughout the implementation.
Thank you for contributing to Neko, you just helped us make RWAs consumer friendly on Stellar! We hope you can continue contributing to this project.