No description provided.
Match a Unicode property or property alias to its canonical property name per the algorithm used for RegExp Unicode property escapes in ECMAScript.
fast and safe way to escape and unescape &<>'" chars
Define a non-enumerable property on an object. Uses Reflect.defineProperty when available, otherwise Object.defineProperty.
A waiting plugin for Cypress
Git commit, but play nice with conventions.
Synchronous file comparison
Easily start and stop an X Virtual Frame Buffer from your node apps.
Specify properties for which a variable, function, keyword or value must be used
mutex lock for javascript
Array methods for ES6 Iterators
A base class utility that manages events and options in modules.
Get a list of packages from a monorepo
Bindings to native Mac/Linux/Windows password APIs
Large collection of predicates.
A Karma plugin. Launcher for Firefox.
Extracts browser and operating system information from the user agent string or user agent object(userAgentData).
Algorithm for finding the root of a yarn workspace, extracted from yarnpkg.com
A module that checks the diff when values are added, removed, or changed in an array.
Generate an index from a directory
Returns true if a value exists, false if empty. Works with deeply nested values using object paths.
Node.js Streams, a user-land copy of the stream library from Node.js
React support for Okta
A module that checks diff when child elements are added, removed, or changed
Release RubyGems via Travis-CI with a Rake task
A simple project to test auto building and release using GitHub and Travis-CI. The goal is to fully automate test, build, and release as the result of a tag push. The release needs to have release artifacts including the gem, docs, and release notes.
Travis CI build stages demo gem release.
Develop on .pre branches, only allow releases from non-.pre clean, up-to-date master. Designed to allow Travis CI to do the push when on a release version, after passing tests.
This ruby client allows you to trigger DataTrue tests from a Continuous Integration tool such as Jenkins, Teamcity, Travis CI, Codeship and others. If you’re practicing Continuous Delivery, it can be used to trigger a test of your application as soon as changes are released.
# Rack::ReadOnly This gem allows Rack based APIs to be set to read only. At the most basic it can be used like this from your `config.ru`: ```ruby require 'rack/read_only' use Rack::ReadOnly, { active: ENV["READ_ONLY"] == "1", response_body: '{ "error": "This API is currently in read only mode." }' } run MyApp ``` When in read only mode the API will continue to respond to GET, HEAD, and OPTIONS requests as normal, but reject POST, PUT, DELETE, and PATCH requests with the body specified, and a 503 error code. ## Installation Add this line to your application's Gemfile: ```ruby gem 'rack-read_only' ``` And then execute: $ bundle Or install it yourself as: $ gem install rack-read_only ## Development After checking out the repo, run `bin/setup` to install dependencies. To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release` to create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org). ## Contributing 1. Fork it ( https://github.com/jellybob/rack-read_only/fork ) 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 a new Pull Request Any new builds should pass the tests on [Travis](https://travis-ci.org/jellybob/rack-read_only)
Helpers to read debian control files
SpreePiwik ========== Adds piwik tracking with Ecommerce tracking Status ------ [](https://travis-ci.org/berkes/spree_piwik) [](https://codeclimate.com/github/berkes/spree_piwik) Installation ------------ Add spree_piwik to your Gemfile: ```ruby gem 'spree_piwik' ``` Bundle your dependencies and run the installation generator: ```shell bundle bundle exec rails g spree_piwik:install ``` Add your Piwik URL and site-id to the `config/initializers/spree_piwik.rb` For example: ```ruby Spree::Piwik::Config[:piwik_url] = "piwik.example.com" Spree::Piwik::Config[:piwik_id] = 1337 ``` Will use http(s)://piwik.example.com/ as url for your Piwik. And track stats for the site that has the id 1337 in Piwik. Screenshot ---------- . Testing ------- First bundle your dependencies, then run `rake`. `rake` will default to building the dummy app if it does not exist, then it will run specs. The dummy app can be regenerated by using `rake test_app`. ```shell bundle bundle exec rake ``` When testing your applications integration with this extension you may use it's factories. Simply add this require statement to your spec_helper: License ------- SpreePiwik is released under the [New BSD License](https://github.com/spree/spree/blob/master/license.md) similar to Spree.
Diff and patch tables
Diff and patch tables