You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@hdunham I tried to spin the API up locally and test the endpoints, but I'm getting a "connection refused" error. The same GET request to the staging and production servers got a good response for the existing /help endpoint. You've tested this locally?
@hdunham I tried to spin the API up locally and test the endpoints, but I'm getting a "connection refused" error. The same GET request to the staging and production servers got a good response for the existing /help endpoint. You've tested this locally?
That's weird, yeah I did test it locally. Let me look again.
@hdunham I tried to spin the API up locally and test the endpoints, but I'm getting a "connection refused" error. The same GET request to the staging and production servers got a good response for the existing /help endpoint. You've tested this locally?
That's weird, yeah I did test it locally. Let me look again.
Oh I guess checking if this ended up working for you when you looked at it again?
@hdunham I tried to spin the API up locally and test the endpoints, but I'm getting a "connection refused" error. The same GET request to the staging and production servers got a good response for the existing /help endpoint. You've tested this locally?
That's weird, yeah I did test it locally. Let me look again.
Oh I guess checking if this ended up working for you when you looked at it again?
Yeah I've tested it many times and it's always worked
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
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.
Please check if the PR fulfills these requirements
What kind of change does this PR introduce?
feature
What is the current behavior?
no erp/inputs (same as erp/help) or erp/outputs urls in the API
What is the new behavior (if this is a feature change)?
erp/inputs (same as erp/help) or erp/outputs urls added
Does this PR introduce a breaking change?
no
Other information:
once merged, update wiki adding
Get descriptions of possible ERP inputs: /erp/inputs?
Get descriptions of possible ERP outputs: /erp/outputs?
here:
https://github.com/NREL/REopt_API/wiki/1.-Structure-of-the-REopt-API#api-endpoints