-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release #99
Conversation
Fixing some not updated info in README.md and removing unnecesary commands from the actions
Adding the .env to the service deployment
Little fixes into the README.md and deploy.yml to tear-down the containers correctly
- Included an openapi.yaml file with the v0.2.0 of the specification - Some changes in the gateway.js to create the swagger sever - Added --pull always option to the README
* Sync package-lock.json
- Reemplace the host IP for production in the specification file - Changed the routes to avoid Fnotfound during the E2E test suite execution
Configuración del fin de partida, CSS de las pantallas
Documentación, filtro de peticiones y post cambiados por gets
app.get('/getgamehistory/:username', async (req, res) => { | ||
try { | ||
const username = req.params.username; | ||
const userResponse = await axios.get(`${userServiceUrl}/getgamehistory/${username}`); |
Check warning
Code scanning / SonarCloud
Server-side requests should not be vulnerable to forging attacks
Quality Gate failedFailed conditions See analysis details on SonarCloud Catch issues before they fail your Quality Gate with our IDE extension SonarLint |
app.get('/getgamehistory/:username', async (req, res) => { | ||
try { | ||
const username = req.params.username; | ||
const userResponse = await axios.get(`${userServiceUrl}/getgamehistory/${username}`); |
Check warning
Code scanning / SonarCloud
Server-side requests should not be vulnerable to forging attacks Medium
No description provided.