PR de contribución con nuevo endpoint de filtrado por stack #173
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
El primer paso fue la creación de los nuevos métodos en el controlador ExplorerController.js y el servicio ExplorerService.js, agregué un método estático en ExplorerController (el cual recibe el stack para filtrado) para consumir el servicio ExplorerService.
En ExplorerService agregué un método estático que recibe la lista de explorers y el stack que será el criterio de filtrado.
Esta función llama a su vez otra función que hace el filtrado de la lista de explorers con el stack como argumento, posteriormente se realiza un mapeo de este resultado para obtener el username y el stack de los usuarios con el stack de criterio seleccionado.