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

Ensure backwards compatibility with v3 and v4 backends #1619

Open
sbliven opened this issue Oct 21, 2024 · 0 comments
Open

Ensure backwards compatibility with v3 and v4 backends #1619

sbliven opened this issue Oct 21, 2024 · 0 comments
Assignees

Comments

@sbliven
Copy link
Contributor

sbliven commented Oct 21, 2024

Ensure backwards compatibility with v3 and v4 backends

Summary

Backend v4 introduces some breaking changes. Off the top of my head:

  1. new /api/v4 base URL if Upgrade API version to v4 scicat-backend-next#1101 approved
  2. Authentication requires "accessTokenPrefix": "Bearer "
  3. job DTO change (release-job branch)

Since backend v3 is expected to be supported for a while still, the frontend should support both versions without recompilation.

Changes needed

  1. Upgrade API version to v4 scicat-backend-next#1101 should include a new frontend configuration to set the global prefix (default "api/v4")
  2. No changes needed (already configurable)
  3. Jobs components should accept either v3 or v4 DTOs in the frontend

So practically only (3) is required for this ticket; the others are just included for completeness.

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

No branches or pull requests

2 participants