Skip to content
This repository has been archived by the owner on Jun 14, 2024. It is now read-only.

Feature/api v3 #43

Merged
merged 16 commits into from
Mar 25, 2019
Merged

Conversation

kamilbednarz
Copy link
Collaborator

Hey @relrod,

here is a draft of a pull request that covers the migration to API v3.

I also refactored the code (separated the logic responsible for HTTP requests/responses) and the organized specs (mostly just wrapped them in describe blocks by method).

@kamilbednarz kamilbednarz requested a review from relrod March 3, 2019 00:13
@kamilbednarz kamilbednarz marked this pull request as ready for review March 3, 2019 00:18
@kamilbednarz kamilbednarz self-assigned this Mar 3, 2019
@relrod
Copy link
Owner

relrod commented Mar 14, 2019

@kamilbednarz At a quick glance this looks fine to me. I'm a bit out of touch with Ruby practices - is there a way to release a beta version of this and let people test it?

@kamilbednarz
Copy link
Collaborator Author

Sure, I'll release a beta version and test it with a project for my client.

@kamilbednarz kamilbednarz changed the base branch from master to release/6.0.0 March 25, 2019 12:12
@kamilbednarz kamilbednarz merged commit 9aa7408 into relrod:release/6.0.0 Mar 25, 2019
@kamilbednarz kamilbednarz deleted the feature/api-v3 branch March 25, 2019 12:15
@kamilbednarz
Copy link
Collaborator Author

Hey @relrod, I created a new gem version, can you either push it to rubygems, or allow me to push new versions (My email is in my github profile)?

The tag is: 6.0.0.beta.1

@relrod
Copy link
Owner

relrod commented Mar 25, 2019

@kamilbednarz Added you on rubygems. Thanks so much for your work on this!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants