Rack::Lodash

NO LONGER IN DEVELOPMENT, obvs.

Lo-dash CDN script tags and fallback in one neat package. Current version is for Lo-dash v#{Rack::Lodash::LODASH_VERSION}

Master branch:

Because then I don't have to worry about versioning or fallback.

Add this line to your application's Gemfile:

gem 'rack-lodash'

And then, from a command-line, execute:

bundle install

Or even better:

bundle install --binstubs --path vendor

Or install it yourself as:

gem install rack-lodash -r

In your rackup file or Sinatra class (or wherever you like to set up Rack middleware…)

use Rack::Lodash

Then wherever you need the script loaded (like in a layout file):

Rack::Lodash.cdn( env )

That's it. There are more options, check the docs.

This library uses semver to version the library. That means the library version is not an indicator of quality but a way to manage changes. The version of Lo-Dash can be found in the lib/rack/lodash/version.rb file, or via the {Rack::Lodash::LODASH_VERSION} constant.

On top of that, version numbers will also change when new releases of Lo-Dash are supported.

• If Lo-Dash makes a major version jump, then this library will make a minor jump. That is because the API for the library has not really changed, but it is possibly a change that will break things.
• If Lo-Dash makes a minor version jump, then so will this library, for the same reason as above.
• I doubt point releases will be followed, but if so, it will also precipitate a minor jump in this library's version number. That's because even though Lo-Dash feel it's a point release, I'm not them, my responsibility is to users of this library and I'll take the cautious approach of making it a minor version number change.

As an example, if the current library version was 1.0.0 and Lo-Dash was at 2.0.0 and I made a change that I felt was major and breaking (to the Ruby library), I'd bump Rack::Lodash's version to 2.0.0. That the version numbers match between Rack::Lodash and the Lo-Dash script is of no significance, it's just coincidental.
If then Lo-Dash went to v2.1.0 and I decided to support that, I'd make the changes and bump Rack::Lodash's version to 2.1.0. That the version numbers match between Rack::Lodash and the Lo-Dash script is of no significance, it's just coincidental.
If then I made a minor change to the library's API that could be breaking I'd bump it to 2.2.0.
If I then added some more instructions I'd bump Rack::Lodash's version to 2.2.1.
If then Lo-Dash released version 3.0.0, I'd add it to the library, and bump Rack::Lodash's version to 2.3.0.

Only one version of Lo-Dash will be supported at a time. This is because the fallback script is shipped with the gem and I'd like to keep it as light as possible. It's also a headache to have more than one.

So basically, if you want to use a specific version of Lo-Dash, look for the library version that supports it via the {Rack::Lodash::LODASH_VERSION} constant. Don't rely on the version numbers of this library to tell you anything other than compatibility between versions of this library.

1. Fork it
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am 'Add some feature')
4. Push to the branch (git push origin my-new-feature)
5. Create new Pull Request