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

Rails 5 support #70

Merged
merged 7 commits into from
Sep 21, 2016
Merged

Rails 5 support #70

merged 7 commits into from
Sep 21, 2016

Conversation

serggl
Copy link
Member

@serggl serggl commented Sep 21, 2016

  • replaced before_filter usages with before_action
  • added a deprecation warning to GrapeSwaggerRails.options.before_filter option

@serggl
Copy link
Member Author

serggl commented Sep 21, 2016

@dblock this one is a followup to #63. Please advise

@@ -3,10 +3,16 @@
module GrapeSwaggerRails
class Options < OpenStruct
def before_filter(&block)
ActiveSupport::Deprecation.warn('this option is deprecated and going to be removed soon. ' \
Copy link
Member

Choose a reason for hiding this comment

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

Should probably start with a capital T to be consistent and have a period after instead?

Copy link
Member Author

Choose a reason for hiding this comment

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

what should be the time period?

Copy link
Member

Choose a reason for hiding this comment

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

I would change "soon" to "version X.Y.Z", whatever the next major one is.

Copy link
Member Author

Choose a reason for hiding this comment

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

Not sure what will be the next major one, so changed to 0.3.0. Is it ok?

@dblock
Copy link
Member

dblock commented Sep 21, 2016

This looks good. We need an UPGRADING document like https://github.com/ruby-grape/grape/blob/master/UPGRADING.md, could you add one please?

You don't have to fight rubocop, if something doesn't make sense (like a line too long), just run rubocop --auto-gen-config. My workflow is rubocop -a, followed by that.

@serggl
Copy link
Member Author

serggl commented Sep 21, 2016

  • added UPGRADING.md file
  • added a Rails version check in ApplicationController to determine a proper callback to use (Rails 3 does not support before_action)

@dblock dblock merged commit 83617bd into ruby-grape:master Sep 21, 2016
@dblock
Copy link
Member

dblock commented Sep 21, 2016

Merged, thank you.

For versioning pros, what's should we do wrt versioning for this deprecation, should it be 0.3.0 or is deprecating something ok for a minor increment?

@dblock
Copy link
Member

dblock commented Sep 21, 2016

Also @serggl you seem to know what you're doing, want to help out with this project? Maybe cut the next release? If you're up for it tell me your rubygems email and I'll add you to project collaborators.

@serggl
Copy link
Member Author

serggl commented Sep 21, 2016

@dblock according to semantic versioning (semver.org) this should be a minor version increment, so I guess this should be 0.3.0

Also yes, I think I can help a bit with this project since I use grape/swagger a lot in my day to day work. My rubygems email is sergey.glukhov@gmail.com

@dblock
Copy link
Member

dblock commented Sep 22, 2016

Welcome @serggl. If you can bump the version as per semver and make a release following https://github.com/ruby-grape/grape-swagger-rails/blob/master/RELEASING.md that'd be great!

@dblock
Copy link
Member

dblock commented Sep 22, 2016

Also @aschuster3 has been very active in this project, keep things publicly visible, I opened #72 for a release.

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.

3 participants