devise-onesignal 3.1.4 → 3.1.5

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 62af876a85b3e16d953ca16eaf0194d46df5c6074f4e24d341bf6218b4f7b530
4
- data.tar.gz: 0cbd80c7c9adc79d7780afa5b4b698e547b71db3fc3508c6b6ed6e8b4d67461e
3
+ metadata.gz: cd9849d656f3afe0487b2b007a31484a320f3ecb91c1a413e7eecb9728a06219
4
+ data.tar.gz: c292a315ba5e62a6a04db0e51a3022b282e537a4973eef72164192c8945e9f48
5
5
  SHA512:
6
- metadata.gz: d61e40560c478c6f4eb239941df0d47e60304c0ac973e89a33cf942a1cdca0ddf50dfd8b928b69e6c6cfc13e2214a43fec7eb58ca235e7f01a3041863f45a590
7
- data.tar.gz: dfd5c988cba7eb4cadf67594ff58abf8d5f0716b1e03163f18d175c0c5cf265a7db66ab16cfb9a138dc26022e2510bda8a367d1552e9fc6d3464083212045631
6
+ metadata.gz: 21389f2a43e0050bad447613a5be4b848f90fa24a21ba23a528211bb16fc354eba56a860198770b8a7941345b6d6b6d16a9166ece36be93595461edba6b0a84c
7
+ data.tar.gz: 3fb6ddbe84cc95fe956d4bd862b5ad4069211d7d1cd152c6d40f1530bb0f227ad2801dcec73281c369cc638bfa7518ccdb77cfa415c25f119aaa647670c42256
data/CHANGELOG.md CHANGED
@@ -4,6 +4,11 @@
4
4
 
5
5
  * nothing yet
6
6
 
7
+ ### 3.1.5 - 2018-01-06
8
+
9
+ * enhancements
10
+ * cleaning up gem files
11
+
7
12
  ### 3.1.4 - 2018-01-02
8
13
 
9
14
  * bugfixes
@@ -1,5 +1,5 @@
1
1
  module DeviseOnesignal
2
2
 
3
- VERSION = '3.1.4'
3
+ VERSION = '3.1.5'
4
4
 
5
5
  end
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: devise-onesignal
3
3
  version: !ruby/object:Gem::Version
4
- version: 3.1.4
4
+ version: 3.1.5
5
5
  platform: ruby
6
6
  authors:
7
7
  - Jonas Hübotter
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2018-01-02 00:00:00.000000000 Z
11
+ date: 2018-01-06 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: rails
@@ -60,20 +60,9 @@ executables: []
60
60
  extensions: []
61
61
  extra_rdoc_files: []
62
62
  files:
63
- - ".github/issue_template.md"
64
- - ".github/pull_request_template.md"
65
- - ".gitignore"
66
- - ".travis.yml"
67
63
  - CHANGELOG.md
68
- - CODE_OF_CONDUCT.md
69
- - CONTRIBUTING.md
70
- - DEPRECATIONS.md
71
- - Gemfile
72
- - INSTALL.md
73
64
  - LICENSE
74
65
  - README.md
75
- - Rakefile
76
- - devise-onesignal.gemspec
77
66
  - lib/devise-onesignal.rb
78
67
  - lib/devise-onesignal/configuration.rb
79
68
  - lib/devise-onesignal/device_concern.rb
@@ -1,14 +0,0 @@
1
- ### Expected behavior
2
- Tell us what should happen
3
-
4
- ### Actual behavior
5
- Tell us what happens instead
6
-
7
- ### Steps to reproduce
8
- Show a way to reproduce
9
-
10
- ### System configuration
11
-
12
- **Ruby version**:
13
-
14
- **Rails version**:
@@ -1,21 +0,0 @@
1
- ### Summary
2
-
3
- Provide a general description of the code changes in your pull
4
- request... were there any bugs you had fixed? If so, mention them. If
5
- these bugs have open GitHub issues, be sure to tag them here as well,
6
- to keep the conversation linked together.
7
-
8
- ### Other Information
9
-
10
- If there's anything else that's important and relevant to your pull
11
- request, mention that information here. This could include
12
- benchmarks, or other information.
13
-
14
- If you are updating any of the CHANGELOG files or are asked to update the
15
- CHANGELOG files by reviewers, please add the CHANGELOG entry at the top of the file.
16
-
17
- Finally, if your pull request affects documentation or any non-code
18
- changes, guidelines for those changes are [available
19
- here](https://github.com/jonhue/devise-onesignal/blob/master/CONTRIBUTING.md)
20
-
21
- Thanks for contributing to `devise-onesignal`!
data/.gitignore DELETED
@@ -1,8 +0,0 @@
1
- test/debug.log
2
- coverage
3
- rdoc
4
- memory
5
- *.gem
6
- .rvmrc
7
- Gemfile.lock
8
- log
data/.travis.yml DELETED
@@ -1,3 +0,0 @@
1
- language: ruby
2
- rvm:
3
- - 2.3.3
data/CODE_OF_CONDUCT.md DELETED
@@ -1,46 +0,0 @@
1
- # Contributor Covenant Code of Conduct
2
-
3
- ## Our Pledge
4
-
5
- In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
6
-
7
- ## Our Standards
8
-
9
- Examples of behavior that contributes to creating a positive environment include:
10
-
11
- * Using welcoming and inclusive language
12
- * Being respectful of differing viewpoints and experiences
13
- * Gracefully accepting constructive criticism
14
- * Focusing on what is best for the community
15
- * Showing empathy towards other community members
16
-
17
- Examples of unacceptable behavior by participants include:
18
-
19
- * The use of sexualized language or imagery and unwelcome sexual attention or advances
20
- * Trolling, insulting/derogatory comments, and personal or political attacks
21
- * Public or private harassment
22
- * Publishing others' private information, such as a physical or electronic address, without explicit permission
23
- * Other conduct which could reasonably be considered inappropriate in a professional setting
24
-
25
- ## Our Responsibilities
26
-
27
- Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
28
-
29
- Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
30
-
31
- ## Scope
32
-
33
- This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
34
-
35
- ## Enforcement
36
-
37
- Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at help@slooob.com. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
38
-
39
- Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
40
-
41
- ## Attribution
42
-
43
- This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
44
-
45
- [homepage]: http://contributor-covenant.org
46
- [version]: http://contributor-covenant.org/version/1/4/
data/CONTRIBUTING.md DELETED
@@ -1 +0,0 @@
1
- # Contributing
data/DEPRECATIONS.md DELETED
@@ -1,9 +0,0 @@
1
- # Deprecations
2
-
3
- ### 3.0.0 - 2017-12-21
4
-
5
- * `devise_class` configuration method removed
6
-
7
- ### 2.0.0 - 2017-12-19
8
-
9
- * you should now configure devise-onesignal through a `configure` block
data/Gemfile DELETED
@@ -1,7 +0,0 @@
1
- source 'https://rubygems.org'
2
-
3
- git_source :github do |repo_name|
4
- "https://github.com/#{repo_name}"
5
- end
6
-
7
- gemspec
data/INSTALL.md DELETED
@@ -1,21 +0,0 @@
1
- **Thank you for installing devise-onesignal!**
2
-
3
-
4
- There are four wo more steps to take:
5
-
6
- 1) Enter your OneSignal App ID in config/initializers/devise-onesignal.rb
7
- 2) Run `rails g devise_onesignal` and `rails db:migrate`
8
- 3) Add:
9
-
10
- //= require OneSignalSDK
11
- //= require devise-onesignal
12
-
13
- to your javascript index in app/assets/javascripts/application.js
14
- 4) Add:
15
-
16
- has_devices
17
-
18
- to your authentication model
19
-
20
-
21
- Learn more at https://github.com/jonhue/devise-onesignal
data/Rakefile DELETED
@@ -1,10 +0,0 @@
1
- require 'bundler/gem_tasks'
2
- require 'rspec/core/rake_task'
3
-
4
- system 'bundle'
5
- system "gem build devise-onesignal.gemspec"
6
-
7
-
8
- RSpec::Core::RakeTask.new
9
-
10
- task default: :spec
@@ -1,25 +0,0 @@
1
- # -*- encoding: utf-8 -*-
2
- require File.expand_path(File.join('..', 'lib', 'devise-onesignal', 'version'), __FILE__)
3
-
4
- Gem::Specification.new do |gem|
5
- gem.name = 'devise-onesignal'
6
- gem.version = DeviseOnesignal::VERSION
7
- gem.platform = Gem::Platform::RUBY
8
- gem.summary = 'Implement user targeted cross-platform notifications in your Rails app'
9
- gem.description = 'Implement user targeted cross-platform notifications with OneSignal & Devise in your Rails app. This gem can also be used without Devise, but it is primarily intended to be used along with some sort of user-management-system.'
10
- gem.authors = 'Jonas Hübotter'
11
- gem.email = 'jonas.huebotter@gmail.com'
12
- gem.homepage = 'https://github.com/jonhue/devise-onesignal'
13
- gem.license = 'MIT'
14
-
15
- gem.files = `git ls-files`.split("\n")
16
- gem.require_paths = ['lib']
17
-
18
- gem.post_install_message = IO.read('INSTALL.md')
19
-
20
- gem.add_dependency 'rails', '>= 5.0'
21
- gem.required_ruby_version = '>= 2.3'
22
-
23
- gem.add_development_dependency 'rspec', '~> 3.7'
24
- gem.add_development_dependency 'rubocop', '~> 0.52'
25
- end