Skip to content
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

Make schemas optional in transaction pipes and provide more context to transaction pipe processors #89

Closed
KellianDev opened this issue Nov 19, 2024 · 0 comments · Fixed by #95
Assignees
Labels
core A feature/improvement on the core crates.

Comments

@KellianDev
Copy link
Contributor

It's been highlighted to me that some people might want to use transaction pipes without schema matching to be able to get an array of decoded instructions out of a transaction update.

To achieve this:

  1. We will add more context to the transaction processors input type by passing an array of decoded instructions.
  2. We will make schemas optional when creating transaction pipes and make the matched schema data optional in the processor's input type.
@KellianDev KellianDev added the core A feature/improvement on the core crates. label Nov 19, 2024
@KellianDev KellianDev self-assigned this Nov 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core A feature/improvement on the core crates.
Projects
None yet
1 participant