alert_message 1.0.5 → 1.0.6

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: f7f41950d533c0e1c628fbc30c994e9ec04e6f38
-  data.tar.gz: 942a6d831a384b536ca855706cced7c0653b3310
+  metadata.gz: 3d348dccb2882760611a061aca94fa61d9957f60
+  data.tar.gz: 0f70f6cc9872aad1684f9e6f4ce4a4efe7ba5b0c
 SHA512:
-  metadata.gz: ea0a9660a4bfd60d03859feaf232b577e6977deb37bd02a670b38d1999e3f5367587635994b4e639bfdfd06705d57555030a56712d61780df0f99807676ad13a
-  data.tar.gz: f64036bcf9a8d153a65a9da4937f0b2989fdb5a51ae79d0acfd5cdf2a42d10c8379faa47a218e6188f97a1579e424256bfb701d5d02fad93ffffa8f5eba17339
+  metadata.gz: b2f0d083be52b7cfafa254ac2481a84f510e152de363151b58d518ca644340792c735c3b30dbfc656105b676503a160663ebc4fee79d4164172c32fe4507fb1e
+  data.tar.gz: f6f097550ef36fc4fce51d22961751d7faca9a23912538469ebb503e9f9ec45ef4a2d7e53e674ab44a927b08f3c7ec48fc2e14b07d4556d8adde9d98a8b62180

data/.rspec

@@ -0,0 +1,2 @@
+--color
+--require spec_helper

data/Gemfile

@@ -4,3 +4,7 @@ gem 'jquery-rails'
 gem 'sass-rails'
 
 gemspec
+
+group :test do
+  gem 'rspec'
+end

data/README.md

@@ -1,4 +1,6 @@
-# Alert Message
+# [Alert Message](http://rubygems.org/gems/alert_message)
+
+[![Gem Version](https://badge.fury.io/rb/alert_message.svg)](http://badge.fury.io/rb/alert_message)
 
 This is a simple gem for alerts messages.
 
@@ -16,9 +18,17 @@ Run install script:
 
     $ rails g alert_message:install
 
+Rename *app/assets/application.css* to *app/assets/application.css.scss* and add in app/assets/application.css.scss
+
+    *= require alert_message
+
+and in app/assets/application.js
+
+    //= require alert_message
+
 ## How to use
 
-Add to *application.html.erb*
+Add in *application.html.erb*
 
     <%= render "layouts/alerts" %>
 
@@ -28,6 +38,19 @@ To show your alerts, use:
     flash[:notice] = "YOUR MESSAGE"
     flash[:success] = "YOUR MESSAGE"
 
+## Example
+
+    class HomeController < ApplicationController
+      def index
+          flash[:error] = "YOUR MESSAGE"  
+      end
+    end
+
+## Demo
+
+[https://alert-message.herokuapp.com/](https://alert-message.herokuapp.com/)
+
+
 ## Contributing
 
 **Welcome to contribute**
@@ -38,7 +61,6 @@ To show your alerts, use:
 4. Push to the branch (git push origin my-new-feature)
 5. Create new Pull Request
 
-
 ## License
 
 MIT License. Copyright 2014 Luiz Picolo. http://www.luizpicolo.com.br

data/lib/generators/alert_message/templates/alerts.css.scss

@@ -15,7 +15,10 @@ $alert-notice: #2980b9;   // azul
   cursor: pointer;
   @include box-sizing(border-box);
 
-  position: absolute;
+  position: fixed;
+  z-index: 9999;
+  top: 0;
+  left: 0;
 
   width: 100%;
 

data/lib/version/version.rb

@@ -1,5 +1,5 @@
 module AlertMessage
   module Version
-    VERSION = '1.0.5'
+    VERSION = '1.0.6'
   end
 end

data/spec/spec_helper.rb

@@ -0,0 +1,89 @@
+# This file was generated by the `rspec --init` command. Conventionally, all
+# specs live under a `spec` directory, which RSpec adds to the `$LOAD_PATH`.
+# The generated `.rspec` file contains `--require spec_helper` which will cause this
+# file to always be loaded, without a need to explicitly require it in any files.
+#
+# Given that it is always loaded, you are encouraged to keep this file as
+# light-weight as possible. Requiring heavyweight dependencies from this file
+# will add to the boot time of your test suite on EVERY test run, even for an
+# individual file that may not need all of that loaded. Instead, consider making
+# a separate helper file that requires the additional dependencies and performs
+# the additional setup, and require it from the spec files that actually need it.
+#
+# The `.rspec` file also contains a few flags that are not defaults but that
+# users commonly want.
+#
+# See http://rubydoc.info/gems/rspec-core/RSpec/Core/Configuration
+RSpec.configure do |config|
+  # rspec-expectations config goes here. You can use an alternate
+  # assertion/expectation library such as wrong or the stdlib/minitest
+  # assertions if you prefer.
+  config.expect_with :rspec do |expectations|
+    # This option will default to `true` in RSpec 4. It makes the `description`
+    # and `failure_message` of custom matchers include text for helper methods
+    # defined using `chain`, e.g.:
+    # be_bigger_than(2).and_smaller_than(4).description
+    #   # => "be bigger than 2 and smaller than 4"
+    # ...rather than:
+    #   # => "be bigger than 2"
+    expectations.include_chain_clauses_in_custom_matcher_descriptions = true
+  end
+
+  # rspec-mocks config goes here. You can use an alternate test double
+  # library (such as bogus or mocha) by changing the `mock_with` option here.
+  config.mock_with :rspec do |mocks|
+    # Prevents you from mocking or stubbing a method that does not exist on
+    # a real object. This is generally recommended, and will default to
+    # `true` in RSpec 4.
+    mocks.verify_partial_doubles = true
+  end
+
+# The settings below are suggested to provide a good initial experience
+# with RSpec, but feel free to customize to your heart's content.
+=begin
+  # These two settings work together to allow you to limit a spec run
+  # to individual examples or groups you care about by tagging them with
+  # `:focus` metadata. When nothing is tagged with `:focus`, all examples
+  # get run.
+  config.filter_run :focus
+  config.run_all_when_everything_filtered = true
+
+  # Limits the available syntax to the non-monkey patched syntax that is recommended.
+  # For more details, see:
+  #   - http://myronmars.to/n/dev-blog/2012/06/rspecs-new-expectation-syntax
+  #   - http://teaisaweso.me/blog/2013/05/27/rspecs-new-message-expectation-syntax/
+  #   - http://myronmars.to/n/dev-blog/2014/05/notable-changes-in-rspec-3#new__config_option_to_disable_rspeccore_monkey_patching
+  config.disable_monkey_patching!
+
+  # This setting enables warnings. It's recommended, but in some cases may
+  # be too noisy due to issues in dependencies.
+  config.warnings = true
+
+  # Many RSpec users commonly either run the entire suite or an individual
+  # file, and it's useful to allow more verbose output when running an
+  # individual spec file.
+  if config.files_to_run.one?
+    # Use the documentation formatter for detailed output,
+    # unless a formatter has already been configured
+    # (e.g. via a command-line flag).
+    config.default_formatter = 'doc'
+  end
+
+  # Print the 10 slowest examples and example groups at the
+  # end of the spec run, to help surface which specs are running
+  # particularly slow.
+  config.profile_examples = 10
+
+  # Run specs in random order to surface order dependencies. If you find an
+  # order dependency and want to debug it, you can fix the order by providing
+  # the seed, which is printed after each run.
+  #     --seed 1234
+  config.order = :random
+
+  # Seed global randomization in this process using the `--seed` CLI option.
+  # Setting this allows you to use `--seed` to deterministically reproduce
+  # test failures related to randomization by passing the same `--seed` value
+  # as the one that triggered the failure.
+  Kernel.srand config.seed
+=end
+end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: alert_message
 version: !ruby/object:Gem::Version
-  version: 1.0.5
+  version: 1.0.6
 platform: ruby
 authors:
 - Luiz Picolo
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-10-31 00:00:00.000000000 Z
+date: 2014-11-26 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -46,6 +46,7 @@ extensions: []
 extra_rdoc_files: []
 files:
 - ".gitignore"
+- ".rspec"
 - Gemfile
 - LICENSE
 - README.md
@@ -58,6 +59,7 @@ files:
 - lib/generators/alert_message/templates/alerts.css.scss
 - lib/generators/alert_message/templates/alerts.js
 - lib/version/version.rb
+- spec/spec_helper.rb
 - vendor/assets/javascripts/alert_message.js
 - vendor/assets/stylesheets/alert_message.css.scss
 homepage: https://github.com/luizpicolo/alert_message