JCN 131 fix al selectear por flags #5
Merged
Conversation
This file contains 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
|
@gastonpereyra ojo que cayó el coverage porque faltaron tests para el código que modificaste.. |
manuelvilche
approved these changes
Aug 7, 2019
jormaechea
requested changes
Aug 8, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
JCN 131-FIX-AL-SELECTEAR-POR-FLAGS
JCN-131 fix al selectear por flags
LINK AL TICKET
https://fizzmod.atlassian.net/browse/JCN-131
DESCRIPCIÓN DEL REQUERIMIENTO
5.1. Se requiere mejorar los filtros por flags, actualmente no esta tomando el valor obtenido en los filtros, sino que aplica siempre el valor de la flag declarada en el modelo
5.2. Se deberá poder filtrar por alguna flag, en donde el value pueda ser 1 y/o 0. ej WHERE (t.flags & 1) = 1) o WHERE (t.flags & 1) = 0)
DESCRIPCIÓN DE LA SOLUCIÓN
Se arregló el código donde no tomaba el valor correcto.