Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RELEASE] v1.3.0 #80

Merged
merged 11 commits into from Apr 11, 2018
Merged

[RELEASE] v1.3.0 #80

merged 11 commits into from Apr 11, 2018

Conversation

mbnakaya
Copy link
Contributor

Description

Release v1.3.0.

Resource::Transfer.new client.get("#{base_path}/#{transfers_id}")
end

def find_all(limit: nil, offset: nil, filters: nil, status: nil)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Esse método de buscar tudo, está me parecendo com muitas responsabilidades. Ele está aplicando uma regra nos parametros recebidos e está transformando a resposta.

Poderíamos tratar esse parametros antes deles serem injetados no find_all? Ou criar um método privado aonde o nome diga o que esta sendo feito para esse tratamento?

A response a mesma coisa, poderíamos criar pelo menos um método privado? Ou tratar ela na camada de cima aonde o find_all está sendo chamado?

Fazendo isso podemos tirar esses comentários tb :)

@mbnakaya mbnakaya merged commit ae4f111 into master Apr 11, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants