Switch to POST method for convert endpoint #143
Merged
+7
−7
Conversation
This file contains hidden or 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
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.
The
/api/freva-nextgen/data-portal/zarr/convertendpoint in freva-rest was changed from GET to POST in the main branch. This PR updates the frontend to use POST requests to maintain compatibility with the latest freva-rest version.This ensures the web interface works correctly with the current freva-rest API. Zarr aggregation and status monitoring features will be introduced in a separate PR since it requires a couple of changes on the API side to the outputs of
/statusendpoint be more user-specified to as a result we be able to make monitoring page of aggregation in each user's profile separately. Otherwise we don't have any other metric to distinguish users history properly.FYI @antarcticrainforest