Issue 51 data availability #70
Merged
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
kan-fu
force-pushed
the
issue-51-data-availability
branch
from
df132f1 to
41b9c20
Compare
kan-fu
force-pushed
the
issue-51-data-availability
branch
from
41b9c20 to
c286c9f
Compare
eliferguson
approved these changes
Nov 14, 2025
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.
Implement #51 for the new API end point https://data.oceannetworks.ca/OpenAPI#get-/dataAvailability/dataproducts.
I am currently using
getDataAvailabilityfor this API. Not sure if there will be data availability for other stuff like/dataAvailability/XXX. Should I usegetDataProductAvailabilityinstead? @aschlesin @elifergusonI also refactored to remove the
methodquery parameter in the API call.