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

Restore Ruby 1.8.7 compatibility with lambda styles etc. #272

Merged
merged 1 commit into from
Aug 11, 2014

Conversation

domcleal
Copy link
Contributor

@domcleal domcleal commented Aug 9, 2014

You'll hate me for this, I know, but 0.2.3 broke 1.8 compatibility in lib/. spec/ had a couple of issues already but otherwise 0.2.2 worked great, despite 87b2158.

@@ -175,7 +175,7 @@ def description
"Must be an array of #{items}"
end

def self.build(param_description, argument, options={}, block)
def self.build(param_description, argument, options, block)
Copy link
Contributor

Choose a reason for hiding this comment

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

what does this change affect?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Nothing AFAICT, as https://github.com/domcleal/apipie-rails/blob/ruby18/lib/apipie/validator.rb#L24 calls this with the options argument every time.

@mtparet
Copy link
Contributor

mtparet commented Aug 11, 2014

1.8.7 has reached its end of life, we should not support it. People should stay with previous version of Apipie-Rails if they wish to use a not maintained Ruby version.
https://www.ruby-lang.org/en/news/2014/07/01/eol-for-1-8-7-and-1-9-2/

@domcleal
Copy link
Contributor Author

I'm fine if you don't want to continue to support it, but I'd not expect support to be dropped in a patch release.

@mtparet
Copy link
Contributor

mtparet commented Aug 11, 2014

but I'd not expect support to be dropped in a patch release

Yes, we should do it in a major release not in a patch release.

@iNecas
Copy link
Member

iNecas commented Aug 11, 2014

@domcleal thanks for going though the code and fixing it for your usecase. The Foreman is one of greatest open-source users of Apipie and we thank it's team to many contributions. I'm ok with this getting in and releaseing 0.2.4, then removing the 1.8.7 from travis and stating, that next release 0.3.x will be not 1.8.7 compatible. If foreman still doesn't say 1.8.7 good-bye in long term, I'm ok with having 0.2.x branch there, and it will need to make sure all the changes it needs are backported to this. On the other hand, I wish you to get over it soon :) What do you think?

@domcleal
Copy link
Contributor Author

@iNecas sounds good to me, thanks!

@iNecas iNecas merged commit 3f896fa into Apipie:master Aug 11, 2014
@iNecas
Copy link
Member

iNecas commented Aug 11, 2014

I've released apipie-rails 0.2.4 that include this changes. I've also included an information that the master and >= 0.3.0 will not further keep the ruby 1.8.7 compatibility https://github.com/Apipie/apipie-rails/blob/master/CHANGELOG.md#-changelog, with possibility to accept backporting to v0.2.x if anyone is wants to spend time one that.

@domcleal
Copy link
Contributor Author

Thanks @iNecas, the help's much appreciated!

@mtparet
Copy link
Contributor

mtparet commented Aug 11, 2014

👍

@komidore64
Copy link
Contributor

@iNecas @domcleal @mtparet thanks to all

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.

4 participants