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

Extend API v1 with endpoints used by new UI #8105

Merged
merged 2 commits into from
Aug 4, 2023

Conversation

vbaranov
Copy link
Member

@vbaranov vbaranov commented Aug 2, 2023

Motivation

There are some Api v1 endpoints which are not under /api/v1 path, b ut they are used in new UI:

  • /graphql
  • /transactions-csv
  • /token-transfers-csv
  • /internal-transactions-csv
  • /logs-csv

In order to simplify devops configuration of proxy between back and front, it is suggested to move them under /api/v1 endpoint

Changelog

  • /graphql -> /api/v1/graphql
  • /transactions-csv -> /api/v1//transactions-csv
  • /token-transfers-csv -> /api/v1/token-transfers-csv
  • /internal-transactions-csv -> /api/v1/internal-transactions-csv
  • /logs-csv -> /api/v1/logs-csv

Checklist for your Pull Request (PR)

@vbaranov vbaranov force-pushed the vb-extend-api-v1-with-endpoints-used-in-new-ui branch 4 times, most recently from 35fb98a to 43d1912 Compare August 3, 2023 10:41
@vbaranov vbaranov force-pushed the vb-extend-api-v1-with-endpoints-used-in-new-ui branch from 84859f4 to 92b38b3 Compare August 4, 2023 11:31
@vbaranov vbaranov merged commit c755bdf into master Aug 4, 2023
15 checks passed
@vbaranov vbaranov deleted the vb-extend-api-v1-with-endpoints-used-in-new-ui branch August 4, 2023 12:57
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.

None yet

1 participant