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

Remove Gemfile.lock and use latest version for dependencies. #28

Closed
wants to merge 6 commits into from

Conversation

mitfik
Copy link

@mitfik mitfik commented Oct 21, 2014

Storing Gemfile.lock in the gem is a bad practice as you are limiting that gem
to use the versions which are hardcoded there. If there is no any
contraindications for that the gem should use always latest versions for all
dependencies.

Storing Gemfile.lock in the gem is a bad practice as you are limiting that gem
to use the versions which are hardcoded there. If there is no any
contraindications for that the gem should use always latest versions for all
dependencies.
@mitfik
Copy link
Author

mitfik commented Oct 21, 2014

I tested it only on 2.1.3, when I will find some time I will take a look on other versions.

Robert Mitwicki added 5 commits October 24, 2014 10:20
According to the specification each invalid response should return an json
object ("error") which will provide information what happen on the server.
There is no reason why jimson should take care of that and translate it to
something else. User should expect to receive for each request (no matter if
this response will success or fail, except Notification requests) an json object
with details about status of that response.
@scratchoo
Copy link

How I can merge this pull request to my fork ?

@mitfik
Copy link
Author

mitfik commented Apr 22, 2015

I can send you a PR if you want (just tell which repo), otherwise you can just clone my repo (mitfik:jimson) branch next and merge with this what you have.

@scratchoo
Copy link

@mitfik I forked your repo (https://github.com/mitfik/jimson) so I don't have to do anything :D I am not sure if this repo is still maintained, good idea to create a separate project based on this one. thank you for your response +1

@chriskite chriskite closed this Mar 14, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants