fix(lookup): resolve disclaimer do lookup para o filtro booleano #1794
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
CSimoesJr
force-pushed
the
lookup/DTHFUI-7511
branch
from
9ec951d to
73ebeeb
Compare
jnrpalma
previously approved these changes
Aug 25, 2023
jcorrea97
previously approved these changes
Aug 28, 2023
Ajusta label do filtro booleano no disclaimer do lookup fixes DTHFUI-7511
CSimoesJr
force-pushed
the
lookup/DTHFUI-7511
branch
from
e747c28 to
bdbfd4d
Compare
jcorrea97
approved these changes
Aug 29, 2023
rafaellmarques
approved these changes
Aug 29, 2023
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.
PO-LOOKUP-MODAL
fixes DTHFUI-7511
PR Checklist [Revisor]
Qual o comportamento atual?
Após realizar algum filtro na busca avançada do lookup, o resultado no disclaimer é apenas o valor e se for do tipo booleano aparece o valor true ou false ao invés das propriedades 'booleanTrue' ou 'booleanFalse'. Exemplo: O campo do tipo booleano com o nome de 'Tem carro' com os valores do switch sendo 'Sim' para true e 'Não' para false aparece no disclaimer quando filtrado somente 'true'
Qual o novo comportamento?
Após realizar algum filtro na busca avançada do lookup, o resultado no disclaimer é a label concatenada com o valor e se for do tipo booleano aparece o valor das propriedades 'booleanTrue' ou 'booleanFalse'. Exemplo: O campo do tipo booleano com o nome de 'Tem carro' com os valores do switch sendo 'Sim' para true e 'Não' para false aparece no disclaimer quando filtrado 'Tem carro: Sim'.
Simulação
app.zip