Skip to content
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

User solutions sending mechanism #472

Closed
jonatanvicente opened this issue Nov 6, 2024 · 1 comment · Fixed by #484
Closed

User solutions sending mechanism #472

jonatanvicente opened this issue Nov 6, 2024 · 1 comment · Fixed by #484
Assignees
Labels
bug Something isn't working Epic 1 Epic 1 Level 1 Level 1 Programming Programming Refactoring Refactoring

Comments

@jonatanvicente
Copy link
Collaborator

jonatanvicente commented Nov 6, 2024

We need to implement a mechanism to know at the moment which challenges contain a solution sended by user.

TASKS TO IMPLEMENT

  • When user executes log In, then we need to know which challenges user sent his solution. For that, we will request to endpoint /itachallenge/api/v1/user/{idUser}/challenges/solutions (by now may be use a dummy, that endpoint is not yet in production).
  • The result will be saved in a variable into a User Service
  • User service must be contains a method to know if user sent a solution for a determinate challenge (that returns boolean). This method should be requested by all components needs it.

BUG TO FIX

  • Ussually, when user is logged in may see all solutions from all challenges. This working is wrong, because may be a user sent a solution to a concrete challenge, but not to all (and not should see all the solutions). It's necessary to fix that.
@jonatanvicente jonatanvicente converted this from a draft issue Nov 6, 2024
@jonatanvicente jonatanvicente added bug Something isn't working Epic 1 Epic 1 Programming Programming Refactoring Refactoring Level 1 Level 1 labels Nov 6, 2024
@xapolin1979 xapolin1979 self-assigned this Nov 6, 2024
@adptCode
Copy link
Collaborator

In the dummy data, the first three challenges are set as having a solution submitted by the user. For these challenges, the button behavior accurately reflects the 'solution sent' status. For all other challenges, the buttons follow a reactive behavior and correctly update based on the solution submission status.

@adptCode adptCode self-assigned this Nov 14, 2024
@adptCode adptCode linked a pull request Nov 14, 2024 that will close this issue
@adptCode adptCode removed a link to a pull request Nov 14, 2024
@adptCode adptCode linked a pull request Nov 14, 2024 that will close this issue
@jonatanvicente jonatanvicente changed the title User solutions sended mechanism User solutions sending mechanism Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Epic 1 Epic 1 Level 1 Level 1 Programming Programming Refactoring Refactoring
Projects
Development

Successfully merging a pull request may close this issue.

3 participants