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

Prevent double clicks when signing contracts; Don't explode on double clicks #23

Closed
wants to merge 3 commits into from
Closed

Prevent double clicks when signing contracts; Don't explode on double clicks #23

wants to merge 3 commits into from

Conversation

Dantemss
Copy link
Member

No description provided.

@coveralls
Copy link

Coverage Status

Coverage decreased (-2.2%) to 79.562% when pulling 489f716 on Dantemss:prevent_double_clicks into fc2f5c2 on lml:master.

@@ -16,7 +16,7 @@ Gem::Specification.new do |s|
s.files = Dir['{app,config,db,lib}/**/*'] + ['MIT-LICENSE', 'Rakefile', 'README.md']
s.test_files = Dir['spec/**/*']

s.add_dependency 'rails', '>= 3.1'
s.add_dependency 'rails', '>= 3.1', '< 5.0'
Copy link
Contributor

Choose a reason for hiding this comment

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

What's the reasoning for restricting Rails to < 5?

Copy link
Contributor

Choose a reason for hiding this comment

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

@Dantemss I have just answered my own question by looking at the commit messages... my question may be ignored. However!!! If you look at the PR I submitted (#24), I migrated away from Squeel to BabySqueel, which is supported in Rails > 5, so the Rails restriction can be removed if my PR is merged. Thoughts?

Copy link
Member Author

Choose a reason for hiding this comment

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

I will rebase and merge after merging yours.

@Dantemss Dantemss closed this Jun 18, 2018
@Dantemss Dantemss deleted the prevent_double_clicks branch June 18, 2018 22:46
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