feat: api used to query ENA REST API for data #310 #402
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.
This pull-request introduces API calls for accessing the ENA REST API. I placed them here because ENA requires cross-site validation, and I encountered errors when making the calls directly from the component. From what I understand, this issue arises because the component runs on the client side rather than the server. There may be alternative solutions, but this approach resolves the problem for now.
Spin up dev environment
Perform request against api
Once this is merged, I will submit a pull request with the component that constructs the query string and displays the data.
There's one change that I would like to do and that is to make the following part configurable:
How would I implement this to make it fit into how brc-analytics is configured?
Example of return data
command:
curl -d '{"filter":"tax_id=65658"}' -X POST http://127.0.0.1:3000/apis/interface/ena | jq