fix(bug 46): Campo de ID aceitando caracteres especiais na criação de perguntas de extração de dados#558
Merged
diegocomis merged 2 commits intoThoth2023:developfrom May 26, 2025
Conversation
diegocomis
approved these changes
May 26, 2025
Collaborator
diegocomis
left a comment
diegocomis
left a comment
There was a problem hiding this comment.
OK, conflitos corrigidos e disponibilizado para merge.
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
2 participants
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.
Anteriormente, o placeholder do campo ID continha apenas uma recomendação para não utilizar caracteres especiais, entretanto, permitia a criação de perguntas com estes.
Modifiquei o placeholder para "ID", padronizando com outras modals, e adicionei validações no backend para impedir a criação de perguntas com IDs que contenham caracteres especiais.