Correção do processamento de registros de mapeamento com valores negativos #61
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
…o flutuante e números negativos
William-Fernandes252
temporarily deployed
to
STAGE
GitHub Actions
Inactive
William-Fernandes252
temporarily deployed
to
STAGE
GitHub Actions
Inactive
|
Visit the preview URL for this PR (updated for commit 44bf7f0): https://tt-linefollower-dev--pr61-fix-deserializacao-d-9t1gfd0q.web.app (expires Sat, 03 Feb 2024 21:45:17 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: e52f592e08b2d312c8d4429239baadff48aa423d |
Matheus-de-Sousa
approved these changes
Jan 5, 2024
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.
Na deserialização dos registros de mapeamento, feita através do método
deserializeRecord, assumia-se que o robô retorna apenas números inteiros positivos. Como alguns campos podem conter valores negativos e/ou valores de ponto flutuante a leitura do mapeamento estava falhando em certos casos. Nesse pull request isso foi corrigido modificando a regex utilizada no método de modo a extrair corretamente qualquer valor numérico.