fix(bug01): Crash in export button without papers, fix(bug03) Add Question Option with question undefinded#556
Merged
diegocomis merged 1 commit intoThoth2023:developfrom May 26, 2025
Conversation
…o e reset dos campos de opcao de pergunta de extracao de dados
diegocomis
approved these changes
May 26, 2025
Collaborator
diegocomis
left a comment
diegocomis
left a comment
There was a problem hiding this comment.
OK, sem conflitos e disponível 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.
In these commits, I fixed the 500 server error that occurred when clicking the Export buttons for CSV, XML, or PDF (bug01). Now, before exporting, the method checks whether the papers array is empty: if it is, a toast with a specific error message is shown; if not, the export proceeds normally. Bug03 was caused by the form fields not being properly reseted. I have fixed this issue as well.