Security News
Oracle Drags Its Feet in the JavaScript Trademark Dispute
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
By Sarah Gooding - Feb 07, 2025
New Case Study:See how Anthropic automated 95% of dependency reviews with Socket.Learn More →
growlyflash
- 0.10.1
- Rubygems
Growlyflash
The growlyflash gem turns boring ActionDispatch::Flash messages in your Rails app to asynchronous Growl-like notifications with Bootstrap Alert markup.
With XHR requests it places flash hash to the X-Messages HTTP header or inline in javascript.
Based on rewritten in coffeescript Bootstrap Growl plugin and inspired by Bootstrap Flash Messages
Update from versions below 0.5.0
Warning! Current version breaks integration from older releases, so, if you want to update, you should check installation and customization steps again.
Installation
Add this line to your application's Gemfile:
gem 'growlyflash'
Require one of the following Growlyflash javascripts depending on your Bootstrap version in app/assets/javascripts/application.js:
For Bootstrap 3
//= require growlyflash
For Bootstrap 2
//= require growlyflash.bs2
Import Growlyflash style in app/assets/stylesheets/application.css.scss after importing Bootstrap styles:
@import "growlyflash";
To use text flash messages as growl notifications with XHR request, add use_growlyflash to your controllers (usually application_controller.rb). This is a shorthand for append_after_action :flash_to_header, if: "request.xhr?" and takes callback parameters like only, except, if or unless:
use_growlyflash # except: %i[actions without growlyflash]
# Also there is another shorthand, to skip callbacks:
# skip_growlyflash only: %i[actions without growlyflash]
To make notifications also available with non-XHR requests, insert the following line into your layout template inside <head> tag before any other javascript:
<%= growlyflash_static_notices %>
If you want your website to be compliant with Content-Security-Policy, and
especially avoid script-src: 'unsafe-inline', you can use another helper to
render an html tag with data attributes instead of injecting javascript code
into your page:
<%= growlyflash_tag %>
Customize
If you want to change default options, you can override them somewhere in your coffee/js:
Growlyflash.defaults = $.extend on, Growlyflash.defaults,
align: 'right' # horizontal aligning (left, right or center)
delay: 4000 # auto-dismiss timeout (0 to disable auto-dismiss)
dismiss: yes # allow to show close button
spacing: 10 # spacing between alerts
target: 'body' # selector to target element where to place alerts
title: no # switch for adding a title
type: null # bootstrap alert class by default
class: ['alert', 'growlyflash', 'fade']
Also you can override few style variables before the @import directive (or just manually override styles (look at _growlyflash.scss):
$growlyflash-top: 20px !default;
$growlyflash-side: 20px !default;
$growlyflash-width: auto !default;
$growlyflash-zindex: 9999 !default;
@import "growlyflash";
Insert the following if you want to close alert boxes by clicking on themselves. Also it doesn't steel focus from toggled elements like dropdowns and works fine with touch devices, so I advise to use it:
jQuery ->
$(document).on "touchstart.alert click.alert", ".growlyflash", (e) ->
e.stopPropagation()
($ @).alert 'close'
off
Contributing
- Fork it
- Create your feature branch (
git checkout -b my-new-feature) - Commit your changes (
git commit -am 'Add some feature') - Push to the branch (
git push origin my-new-feature) - Create new Pull Request
FAQs
Unknown package
We found that growlyflash demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Package last updated on 07 May 2019
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Related posts
Security News
Linux Foundation Warns Open Source Developers: Compliance with Sanctions Is Not Optional
The Linux Foundation is warning open source developers that compliance with global sanctions is mandatory, highlighting legal risks and restrictions on contributions.
By Sarah Gooding - Feb 06, 2025
Security News
Maven Central Adds Sigstore Signature Validation
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.
By Sarah Gooding - Feb 06, 2025