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

Refs #1021 - Fixes the rubocop violation 'Style/StringLiterals' #1027

Conversation

pmatsinopoulos
Copy link

@pmatsinopoulos pmatsinopoulos commented Sep 20, 2016

Summary

Fixed the Style/StringLiteral rubocop offending code.

Details

Motivation and Context

This change fix part of #1021. It does not fix it completely, but only partially. Other PRs will follow on same issue.

How Has This Been Tested?

No new tests have been added. But existing tests run green. Also rubocop is happy with the Style/StringLiterals enabled.

Screenshots (if appropriate):

N/A

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Style changes to make rubocop happy.

Checklist:

  • I've added tests for my code
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.

@mattwynne
Copy link
Member

@cucumber/cucumber-ruby would any of you like to help merge these in? You all have the appropriate permissions!

@mattwynne
Copy link
Member

Thanks a lot @pmatsinopoulos - keep them coming, we appreciate it!

@brasmusson
Copy link
Contributor

@pmatsinopoulos You need to careful when you write the PR description, you used "fix #1021", that is a wording that will trigger Github to automatically close the referred issue when the RP is merged. I changed it to "fix part of #1021" to inhibit Github to do that.

@pmatsinopoulos
Copy link
Author

pmatsinopoulos commented Sep 22, 2016

@brasmusson

@pmatsinopoulos You need to careful when you write the PR description

Ooooh! Didn't know that. Sorry. Thanks for letting me know! Will definitely make sure will not happen again.

@mattwynne
Copy link
Member

any chance you could rebase this @pmatsinopoulos?

@pmatsinopoulos
Copy link
Author

any chance you could rebase this @pmatsinopoulos?

@mattwynne gladly will do that. But will be tomorrow. I am travelling today.

@pmatsinopoulos pmatsinopoulos force-pushed the fix-style-violation-1021-style-string-literals branch from 6dd4993 to d12b847 Compare September 23, 2016 11:40
@pmatsinopoulos
Copy link
Author

@mattwynne I finally did that a while ago. Conflicts with master have been resolved.

@nodo
Copy link
Member

nodo commented Sep 27, 2016

Hi @pmatsinopoulos, I am sorry I have been merging some other PRs about style and now your PR has conflicts again. Please, could you resolve the conflicts and rebase? As soon as you do it I will get it merged.

Thanks a lot for your work, really appreciated.

@pmatsinopoulos pmatsinopoulos force-pushed the fix-style-violation-1021-style-string-literals branch from d12b847 to 700231f Compare September 27, 2016 17:47
@pmatsinopoulos
Copy link
Author

@nodo Ready. No problem!

@nodo
Copy link
Member

nodo commented Sep 28, 2016

Thanks a lot @pmatsinopoulos ! Looks good 👍

@nodo nodo merged commit 2c420d6 into cucumber:master Sep 28, 2016
@pmatsinopoulos pmatsinopoulos deleted the fix-style-violation-1021-style-string-literals branch September 29, 2016 04:56
@lock
Copy link

lock bot commented Oct 25, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Oct 25, 2018
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.

4 participants