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

Type IPricesApi/IBalancesApi responses as "raw" #2100

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

iamacook
Copy link
Member

@iamacook iamacook commented Nov 7, 2024

Partial implementation of #1731

Summary

We validate API responses on the domain layer, but directly assign the type in the datasources. This means that the response types are not necessarily correct.

This types all request responses of IPricesApi/IBalancesApi as "raw". These responses are therefore not be used directly unless they are validated.

Not: these are combined as they are heavily interlinked.

Changes

  • Add Raw utility type to IStakingApi
  • Add Raw utility type to IBalancesApi
  • Update validation where appropriate
  • Update tests accordingly

@iamacook iamacook self-assigned this Nov 7, 2024
@iamacook iamacook requested a review from a team as a code owner November 7, 2024 08:34
@iamacook iamacook marked this pull request as draft November 7, 2024 08:51
@iamacook iamacook changed the title Type IPricesApi responses as "raw" Type IPricesApi/IBalancesApi responses as "raw" Nov 7, 2024
});

expect(networkService.get.mock.calls.length).toBe(4);
expect(networkService.get.mock.calls.length).toBe(3);
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These will be addressed by adjusting the HttpErrorFactory.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good to me, and I'm pretty sure you are aware, but just something to have in mind: I'd say we need to be cautious there and avoid exposing the details of a ZodError when the validation failure comes from an error while processing a Datasource response (e.g.: a Transaction Service response), to avoid leaking data through the public route controller 👍🏻

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Totally agree with you!

@iamacook iamacook marked this pull request as ready for review November 7, 2024 10:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants