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

Add new fetchMethod to specify legacy gateways #275

Open
bdrhn9 opened this issue Oct 12, 2022 · 1 comment
Open

Add new fetchMethod to specify legacy gateways #275

bdrhn9 opened this issue Oct 12, 2022 · 1 comment

Comments

@bdrhn9
Copy link
Contributor

bdrhn9 commented Oct 12, 2022

Current implementation has two fetchMethod, api and gateway. When gateway is selected, the requester function tries to parse response with legacy schema as in here. If it fails, then it tries with the current schema. Adding an extra fetchMethod like gateway-old, we can distinctly select the schema going to be utilized for parsing.

@aquarat
Copy link
Contributor

aquarat commented May 31, 2023

As noted in the meeting, this is low priority as the only side effect of the current situation is reduced compute efficiency.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants