feat(repo): Introduce FuelStreams Types #320
Open
+2,206
−1,391
Conversation
This file contains 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
…aphQL's This change introduces Block, Transaction, Receipt, Utxo, Log, Input, Output structs instead of exposing fuel-core's for stream consumers. We cache and aggregate all necessary fields in these structures and try to align them with their respective GraphQL's interfaces.
Jurshsmith
requested review from
luizstacio,
pedronauck and
0xterminator
as code owners
Jurshsmith
force-pushed
the
aj/DS-113/introduce-core-fuel-streams-types
branch
from
ed646cd
to
82e9bfd
Compare
Jurshsmith
force-pushed
the
aj/DS-113/introduce-core-fuel-streams-types
branch
from
e8563d9
to
9785d79
Compare
Jurshsmith
force-pushed
the
aj/DS-113/introduce-core-fuel-streams-types
branch
from
9785d79
to
ec728d9
Compare
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.
Currently,
fuel-coretypes are directly exposed to users for streaming. However, this approach has several drawbacks:fuel-coretypes could mislead users into assuming related APIs, which require a configured environment, are usable directly with streams.This PR addresses these issues by introducing
FuelStreamstypes, designed as aggregation types optimized for broad use cases. These types are derived from the GraphQL interface used in frontend projects, ensuring a structured and user-friendly format.Moving forward, we will expand these types to include additional fields based on user needs, making them more versatile and compatible across different integrations.
Closes DS-113
Subtasks:
Closes DS-114, DS-115, DS-116, DS-117, DS-118