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
When running front-end dev environment we've faced a problem that is related to the configuration the project established as standard. This error happens specifically on file url_routes.js when trying to import the variable REACT_APP_URL_API.
This variable is mentioned on project's README file, to be set on the docker-compose.yml file according to the server where the API is running.
But, even when setting the correct server, all the requisitions made to the API are made to a broken URL.
This error happens here:
This usage of the variable brings the adress set, but unites it with an "undefined" word before adding the rest of the path to the API. So, its breaks all the callings to the API.
Although this is a bug that happens when using the dev environment, it does not happen when using docker.
Tasks
Fix the API calling adress without breaking the docker use of it;
Acceptance criteria
Dev environment can communicate with the API;
Front-end docker continues to work correctly;
The text was updated successfully, but these errors were encountered:
When running front-end dev environment we've faced a problem that is related to the configuration the project established as standard. This error happens specifically on file url_routes.js when trying to import the variable REACT_APP_URL_API.
This variable is mentioned on project's README file, to be set on the docker-compose.yml file according to the server where the API is running.
But, even when setting the correct server, all the requisitions made to the API are made to a broken URL.
This error happens here:
FILE: url_routes.js
This usage of the variable brings the adress set, but unites it with an "undefined" word before adding the rest of the path to the API. So, its breaks all the callings to the API.
Although this is a bug that happens when using the dev environment, it does not happen when using docker.
Tasks
Acceptance criteria
The text was updated successfully, but these errors were encountered: