Corrigindo bug da função não responder quando a API estiver instável do BCB#21
Merged
Corrigindo bug da função não responder quando a API estiver instável do BCB#21
Conversation
O CRAN reclamou que a função download deveria existir alguma retorno quando o usuário tentasse usar a API e não funcionasse.
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
1 participant
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.
Essa correção foi solicitada pelo CRAN. Antes a função quando a API do BCB caia ou o usuário tinha uma instabilidade na internet a função retornava um warning. Esse warning não é o correto, agora a função retorna NULL ou um dataframe vazio quando qualquer um dos dois ocorrem.
Essa PULL REQUEST também corrige a descrição das funções, aonde agora o CRAN não vai mais rodar e correr o risco de cair nos testes do CRAN.