Feat/add blocks api #3
Merged
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
Added support for blocks bff api.
Added support for blocks bff api.
lint fixes.
Implemented batch api.
Vitest file paralellism was causing issues with test server. This changes fixed them.
Added stats routes.
Added blind forward for transaction endpoints to unblock front end development.
Added blind forward for all endpoints to facilitate frontend development.
aon
reviewed
Nov 1, 2024
|
|
||
| export function apiRoutes(app: FastifyApp) { | ||
| app.get('/', async (req, reply) => { | ||
| const targetUrl = `${app.conf.proxyTarget}${req.url}`; |
There was a problem hiding this comment.
Does this work without a / in the middle?
There was a problem hiding this comment.
Yes! req.url starts with a slash. always.
aon
approved these changes
Nov 1, 2024
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.
What ❔
Handling all api routes in proxy. There are filters still missing, but this should unblock front end development.
Why ❔
To have the proxy cover all the explorer api.
Checklist