unpoly-rails 0.57.0 → 0.60.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: af0d5493649ecec8227682297684d979b948b1f80bbf9cfeae29f38f7a8d6188
-  data.tar.gz: ef3e30eca247452227534043db0b5e69e4f815299366cedca964fc8c3bc1e9e4
+  metadata.gz: 22a06b1df40b84a4c8afd15b404c65addacb66469f0c374912dc5121ee41fd50
+  data.tar.gz: dec9cd21d854d639d59cb5de63be07f67e42c8dc6bc992de04bb7ac88dc8ac40
 SHA512:
-  metadata.gz: 1393189464a4148ffd4a5bc1392607345b493a31847c999a0f45916c62cb912d255ca39c2ab95a2703007d14ada30930f7313585ac6e4d742e0c9dee2303e374
-  data.tar.gz: 6e42685e20553c08ad58e4d89296ebe009766f602af8e383e6e5a40aafce27dfdde0f186ba56ecadcb41bf9a6648ae0bf3090ea6b8cfb37225c982f7940475e8
+  metadata.gz: f4c3fc420e7eaeb04497ad867c920a48de3c0f21cb0adc85daf58107752f9d7ef9608ac96cf917e6e1b04f6a6e0c5ffb9a649ff1e3ee089cb5f8562a49e259d9
+  data.tar.gz: ca57a9c137357b15a9c2e6935384f00a81422561eabd81bf499f2dcf1427e0c4e2141ee7dda8f87627891adbb3e1bb599fa7dddf729b704d7816a8491db8a634

data/CHANGELOG.md

@@ -3,7 +3,399 @@ Changelog
 
 Changes to this project will be documented in this file.
 
-This project mostly adheres to [Semantic Versioning](http://semver.org/).
+You may browse a formatted and hyperlinked version of this file at <http://unpoly.com/changes>.
+
+
+0.60.0
+------
+
+This is a major update with some breaking changes.
+
+### Highlights
+
+- jQuery is no longer required! Unpoly now has zero dependencies.
+- New `up.element` helpers to complement [native `Element` methods](https://www.w3schools.com/jsref/dom_obj_all.asp). You might not even miss jQuery anymore.
+- Vastly improved performance on slow devices.
+- Utility functions that work with arrays and array-like values have been greatly improved.
+- The `up.util` module now plug the worst emissions in JavaScript's standard library: Equality-by-value, empty-by-value and shallow-copy. Your own objects may hook into those protocols.
+- You may define a padding when [revealing](/up.reveal).
+- Smooth [scrolling](/up.scroll) now mimics [native scroll behavior](https://hospodarets.com/native_smooth_scrolling).
+- Fixed many positioning issues with [popups](/up.popup) and [tooltips](/up.tooltip).
+- Several modules have been renamed to match the pattern `up.thing.verb()`. `up.dom` is now `up.fragment`, `up.bus` is now `up.event`, `up.layout` is now `up.viewport`.
+
+Details below.
+
+
+### jQuery is no longer required
+
+jQuery no longer required to use Unpoly. That means Unpoly no longer has any dependencies!
+
+Due to its use of native DOM APIs, Unpoly is now a lot faster. Like, a **lot**. Ditching jQuery also saves you 30 KB of gzipped bundle size and speeds up your own code.
+
+#### Migrating apps that use jQuery
+
+Effort has been made to ensure that migrating to this version is smooth for existing apps that use jQuery.
+
+All Unpoly functions that accept element arguments will accept both native elements and jQuery collections.
+
+You will need to prefix some function calls with `$` to have your callbacks called with jQuery collections instead of native elements:
+
+- The `up.compiler()` callback now receives a [native element](https://developer.mozilla.org/en-US/docs/Web/API/Element) instead of a jQuery collection. For the old behavior, use `up.$compiler()`.
+- The `up.macro()` callback now received a [native element](https://developer.mozilla.org/en-US/docs/Web/API/Element) instead of a jQuery collection. For the old behavior, use `up.$macro()`.
+- The event handler passed to `up.on()` now receives an element instead of a jQuery collection. For the old behavior, use `up.$on()`.
+
+Finally, all Unpoly events (`up:*`) are now triggered as native events that can be received with [`Element#addEventListener()`](https://developer.mozilla.org/en-US/docs/Web/API/EventTarget/addEventListener). You may continue to use jQuery's [`jQuery#on()`](http://api.jquery.com/on/) to listen to Unpoly events, but you need to access custom properties through `event.originalEvent`.
+
+Also know that if you use jQuery's `$.fn.trigger()` to emit events, these events are not received by native event listeners (including Unpoly). Use `up.emit()` instead to trigger an event that can be received by both native listeners and jQuery listeners.
+
+See below for detailed changes.
+
+
+### New DOM helpers
+
+A new, experimental `up.element` module offers convience functions for DOM manipulation and traversal.
+
+It complements [native `Element` methods](https://www.w3schools.com/jsref/dom_obj_all.asp) and works across all [supported browsers](/up.browser) without polyfills.
+
+| `up.element.first()` |  Returns the first descendant element matching the given selector.|
+| `up.element.all()` |  Returns all descendant elements matching the given selector.|
+| `up.element.subtree()` |  Returns a list of the given parent's descendants matching the given selector. The list will also include the parent element if it matches the selector itself.|
+| `up.element.closest()` |  Returns the first element that matches the selector by testing the element itself and traversing up through its ancestors in the DOM tree.|
+| `up.element.matches()` |  Matches all elements that have a descendant matching the given selector.|
+| `up.element.get()` |  Casts the given value to a native [Element](https://developer.mozilla.org/en-US/docs/Web/API/Element).|
+| `up.element.toggle()` |  Display or hide the given element, depending on its current visibility.|
+| `up.element.toggleClass()` |  Adds or removes the given class from the given element.|
+| `up.element.hide()` |  Hides the given element.|
+| `up.element.show()` |  Shows the given element.|
+| `up.element.remove()` |  Removes the given element from the DOM tree.|
+| `up.element.replace()` |  Replaces the given old element with the given new element.|
+| `up.element.setAttrs()` |  Sets all key/values from the given object as attributes on the given element.|
+| `up.element.affix()` |  Creates an element matching the given CSS selector and attaches it to the given parent element.|
+| `up.element.createFromSelector()` |  Creates an element matching the given CSS selector.|
+| `up.element.createFromHtml()` |  Creates an element from the given HTML fragment.|
+| `up.element.toSelector()` |  Returns a CSS selector that matches the given element as good as possible.|
+| `up.element.setAttrs()` |  Sets all key/values from the given object as attributes on the given element.|
+| `up.element.booleanAttr()` |  Returns the value of the given attribute on the given element, cast as a boolean value.|
+| `up.element.numberAttr()` |  Returns the value of the given attribute on the given element, cast to a number.|
+| `up.element.jsonAttr()` |  Reads the given attribute from the element, parsed as [JSON](https://www.json.org/).|
+| `up.element.style()` |  Receives [computed CSS styles](https://developer.mozilla.org/en-US/docs/Web/API/Window/getComputedStyle) for the given element.|
+| `up.element.styleNumber()` |  Receives a [computed CSS property value](https://developer.mozilla.org/en-US/docs/Web/API/Window/getComputedStyle) for the given element, casted as a number.|
+| `up.element.setStyle()` |  Sets the given CSS properties as inline styles on the given element.|
+| `up.element.isVisible()` |  Returns whether the given element is currently visible.|
+| `:has()` |  A non-standard [pseudo-class](https://developer.mozilla.org/en-US/docs/Learn/CSS/Introduction_to_CSS/Pseudo-classes_and_pseudo-elements) that matches all elements that have a descendant matching the given selector. |
+
+### Events
+
+- The `up.bus` module has been renamed to `up.event`. We want to normalize Unpoly's API to the pattern `up.thing.verb()` in the future.
+- All Unpoly events (`up:*`) are now triggered as native events that can be received with [`Element#addEventListener()`](https://developer.mozilla.org/en-US/docs/Web/API/EventTarget/addEventListener). You may continue to use jQuery's [`jQuery#on()`](http://api.jquery.com/on/) to listen to Unpoly events, but you need to access custom properties from `event.originalEvent`.
+- Properties named `event.$target` and `event.$element` have been removed from *all* Unpoly events.
+  Use the standard `event.target` to retrieve the element on which the element was [emitted](/up.emit).
+- `up.on()` may now bind to a given element by passing it as an (optional) first argument:
+
+  ```
+  up.on(element, '.button', 'click', (event) => { ... })
+  ```
+
+  You may use this for [event delegation](https://davidwalsh.name/event-delegate).
+- The event handler passed to `up.on()` now receives an element instead of a jQuery collection:
+
+  ```
+  up.on('click', (event, element) => {
+    alert("Clicked on an " + element.tagName)
+  })
+  ```
+
+  For the old behavior, use `up.$on()`.
+- `up.emit()` may now trigger an event on a given element by passing the element as an (optional) first argument:
+
+  ```
+  up.emit(element, 'app:user:login', { email: 'foo@example.com' })
+  ```
+- `up.emit()` option `{ message }` is now `{ log }`.
+- `up.emit()` no longer logs by default. You can enable the old efault message with `{ log: true }`.
+- `up.event.nobodyPrevents()` option `{ message }` is now `{ log }`.
+- The experimental function `up.reset()` was removed without replacement.
+- The experimental event `up:framework:reset` was removed without replacement.
+
+
+
+### Custom JavaScript
+
+- [Compilers](/up.compiler) may again return an array of destructor functions. The previous deprecation was removed.
+- The `up.compiler()` callback now receives a [native element](https://developer.mozilla.org/en-US/docs/Web/API/Element) instead of a jQuery collection:
+
+  ```
+  up.compiler('.button', function(button) {
+    alert("We have a new button with class " + button.className)
+  })
+  ```
+
+  For the old behavior, use `up.$compiler()`.
+- The `up.macro()` callback now received a [native element](https://developer.mozilla.org/en-US/docs/Web/API/Element) instead of a jQuery collection:
+
+  ```
+  up.compiler('a.fast-link', function(element) {
+    element.setAttribute('up-preload', 'up-preload')
+    element.setAttribute('up-instant', 'up-instant')
+  })
+  ```
+
+  For the old behavior, use `up.$macro()`.
+
+
+
+### Forms
+
+- `up:form:submit` no longer has a `{ $form }` property. The event is now [emitted](/up.emit)
+  on the form that is being submitted.
+- `up.observe()` now accepts a single form field, multiple fields,
+  a `<form>` or any container that contains form fields.
+  The callback is called once for each change in any of the given elements.
+- The callback for `up.observe()` now receives the arguments `(value, name)`, where
+  `value` is the changed field value and `name` is the `[name]` of the field element:
+
+  ```
+  up.observe('form', function(value, name) {
+    console.log('The value of %o is now %o', name, value);
+  });
+  ```
+
+  The second argument was previously the observed input element as a jQuery collection.
+- `up.observe()` now accepts a `{ batch: true }` option to receive all changes
+  since the last callback in a single object:
+
+  ```
+  up.observe('form', { batch: true }, function(diff) {
+    console.log('Observed one or more changes: %o', diff);
+  });
+  ```
+- The default `up.form.config.validateTargets` no longer includes the
+  selector `'[up-fieldset]'`.
+
+
+### Animation
+
+- CSS property names for custom [animations](/up.animation) and [transitions](/up.transition) must be given in `kebab-case`.
+  `camelCase` properties are no longer supported.
+
+
+### Fragment update API
+
+- The module `up.dom` has been renamed to `up.fragment`. We want to normalize Unpoly's API to the pattern `up.thing.verb()` in the future.
+- The experimental function `up.all()` has been removed without replacement
+- The function `up.first()` has been renamed to `up.fragment.first()` to not be confused
+  with the low-level `up.element.first()`.
+- The event `up:fragment:destroy` has been removed without replacement. This event was previously emitted before a fragment was removed. The event [`up:fragment:destroyed`](/up:fragment:destroyed) (emitted after a fragment was removed), remains in the API.
+- The `up:fragment:destroyed` event no longer has a `{ $element }` property. It now has a `{ fragment }` property that contains the detached element. Like before, it is emitted on the former parent of the destroyed element.
+- The properties for the `up:fragment:keep` event have been renamed.
+- The properties for the `up:fragment:kept` event have been renamed.
+- The properties for the `up:fragment:inserted` event have been renamed.
+- The properties for the `up:fragment:destroyed` event have been renamed.
+
+
+### Utility functions
+
+The `up.util` module now plug the worst emissions in JavaScript's standard library: Equality-by-value, empty-by-value, shallow copy:
+
+- New experimental function `up.util.isEqual()`. It returns whether the given arguments are equal by value.
+- New experimental property `up.util.isEqual.key`.
+  This property contains the name of a method that user-defined classes
+  may implement to hook into the `up.util.isEqual()` protocol.
+- `up.util.isBlank()` now returns false for objects with a constructor.
+- New experimental property `up.util.isBlank.key`. This property contains the name of a method that user-defined classes may implement to hook into the `up.util.isBlank()` protocol.
+- New experimental property `up.util.copy.key`. This property contains the name of a method that user-defined classes may implement to hook into the `up.util.copy()` protocol.
+
+More utility functions to have been added to work with lists:
+
+- New experimental function `up.util.findResult()`.
+  It consecutively calls the given function which each element in the given list and
+  returns the first truthy return value.
+- New experimental function `up.util.flatten()`. This flattens the given list a single level deep.
+- New experimental function `up.util.flatMap()`. This maps each element using a mapping function, then flattens the result into a new array.
+
+Some list functions have been renamed to names used in the standard `Array` API:
+
+- `up.util.all()` was renamed to `up.util.every()` to match the standard [`Array#every()`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/every), and to be less confusing with `up.element.all()`.
+- `up.util.any()` was renamed to `up.util.some()` to match the standard
+  [`Array#some()`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/some).
+- `up.util.select()` was renamed to `up.util.filter()` to match the standard
+  [`Array#filter()`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/filter).
+- `up.util.detect()` was renamed to `up.util.find()` to match the standard
+  [`Array#find()`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/find).
+
+All functions that worked for arrays now also work for array-like values:
+
+- New experimental function `up.util.isList()`. It returns whether the given argument is an array-like value, like an `Array` or a
+  [`NodeList`](https://developer.mozilla.org/en-US/docs/Web/API/NodeList).
+- `up.util.reject()` now works for all [array-like values](/up.util.isList), not just arrays.
+- `up.util.filter()` now works for all [array-like values](/up.util.isList), not just arrays.
+- `up.util.find()` now works for all [array-like values](/up.util.isList), not just arrays.
+- `up.util.some()` now works for all [array-like values](/up.util.isList), not just arrays.
+- `up.util.every()` now works for all [array-like values](/up.util.isList), not just arrays.
+
+And some minor changes:
+
+- `up.util.nextFrame()` has been renamed to `up.util.task()`.
+- `up.util.setTimer()` has been renamed to `up.util.timer()`.
+- `up.util.toArray() now returns its unchanged argument if the argument is already an array.
+- `up.util.copy()` now works with `Date` objects.
+- `up.util.isBoolean()` is now stable
+- `up.util.escapeHtml()` is now stable
+- `up.util.isJQuery()` now returns `false` if no jQuery is loaded into the `window.jQuery` global
+- `up.util.unresolvablePromise()` was removed without replacement.
+- `up.util.trim()` has been removed without replacement. Use the standard
+  [`String#trim()`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/Trim) instead.
+- `up.util.parseUrl()` now returns the correct `{ hostname }`, `{ protocol }` and `{ pathname }` properties on IE11.
+- `up.util.selectorForElement()` is now `up.element.toSelector()`
+
+
+### Scrolling Viewports
+
+- The `up.layout` module has been renamed to `up.viewport`. We want to normalize Unpoly's API to the pattern `up.thing.verb()` in the future.
+- Smooth [scrolling](/up.scroll) now mimics [native scroll behavior](https://hospodarets.com/native_smooth_scrolling):
+  - `up.scroll()` no longer takes a `{ duration }` or `{ easing }` option.
+  - `up.scroll()` now takes a `{ behavior }` option. Valid values are `auto` (no animation) and `smooth` (animates the scroll motion).
+  - You may control the pace of `{ behavior: 'smooth' }` by also passing a `{ speed }` option`.
+  - New config property `up.viewport.scrollSpeed`. This sets the default speed for smooth scrolling. The default value (`1`) roughly corresponds to the default speed of Chrome's native smooth scrolling.
+- Options for `up.reveal()` have been changed:
+  - Options `{ duration }` and `{ easing }` have been removed.
+  - New option `{ padding }` to pass the desired padding between the revealed element and the closest [viewport](/up.viewport) edge (in pixels).
+  - New option `{ snap }`. It can be `true`, `false` or a pixel number.
+  - New option `{ behavior }`
+  - New option `{ speed }`. Defaults to `up.viewport.scrollSpeed`.
+  - Config property `up.layout.config.snap` has been renamed to `up.viewport.config.revealSnap`.
+  - New config option `up.viewport.revealPadding`.
+- New experimental function `up.viewport.root()`. It return the [scrolling element](https://developer.mozilla.org/en-US/docs/Web/API/document/scrollingElement)
+  for the browser's main content area.
+- New experimental function `up.viewport.closest()`. It returns the scrolling container for the given element.
+- When a `#hash` anchor is [revealed](/up.reveal) during the initial page load, Unpoly will look for an `[up-id=hash]` before looking for `[id=hash]` and `a[name=hash]`.
+- Fix issues with restoring scroll positions when going back on some browsers.
+
+
+### Navigation feedback
+
+- [`[up-alias]`](/up-nav#matching-url-by-pattern) now accepts one or more asterisks (`*`) anywhere in the pattern.
+   It was previously limited to match URLs with a given prefix.
+
+
+### Performance
+
+- Use of native browser APIs has improved performance drastically.
+- `[up-preload]` and `[up-instant]` links no longer bind to the `touchstart` event, increasing frame rate while scrolling.
+
+
+### Request parameters
+
+The experimental `up.params` module has been replaced with the `up.Params` class.
+Wrap any type of parameter representation into `up.Params` to get consistent API for reading
+and manipulation.
+
+The following types of parameter representation are supported:
+
+1. An object like `{ email: 'foo@bar.com' }`
+2. A query string like `'email=foo%40bar.com'`
+3. An array of `{ name, value }` objects like `[{ name: 'email', value: 'foo@bar.com' }]`
+4. A [FormData](https://developer.mozilla.org/en-US/docs/Web/API/FormData) object.
+   On IE 11 and Edge, `FormData` payloads require a [polyfill for `FormData#entries()`](https://github.com/jimmywarting/FormData).
+
+Supported methods are:
+
+| `new up.Params()` | Constructor. |
+| `up.Params#add()` | Adds a new entry with the given `name` and `value`. |
+| `up.Params#addAll()` | Adds all entries from the given list of params. |
+| `up.Params#addField()` | Adds params from the given [HTML form field](https://www.w3schools.com/html/html_form_elements.asp). |
+| `up.Params#delete()` | Deletes all entries with the given `name`. |
+| `up.Params#get()` | Returns the first param value with the given `name` from the given `params`. |
+| `up.Params#set()` |  Sets the `value` for the entry with given `name`. |
+| `up.Params#toArray()` | Returns an array representation of this `up.Params` instance. |
+| `up.Params#toFormData()` | Returns a [`FormData`](https://developer.mozilla.org/en-US/docs/Web/API/FormData) representation of this `up.Params` instance. |
+| `up.Params#toObject()` | Returns an object representation of this `up.Params` instance. |
+| `up.Params#toQuery()` | Returns an [query string](https://en.wikipedia.org/wiki/Query_string) for this `up.Params` instance. |
+| `up.Params#toURL()` | Builds an URL string from the given base URL and this `up.Params` instance as a [query string](/up.Params.toString). |
+| `up.Params.fromFields()` | Constructs a new `up.Params` instance from one or more [HTML form field](https://www.w3schools.com/html/html_form_elements.asp). |
+| `up.Params.fromForm()` | Constructs a new `up.Params` instance from the given `<form>`. |
+| `up.Params.fromURL()` | Constructs a new `up.Params` instance from the given URL's [query string](https://en.wikipedia.org/wiki/Query_string). |
+
+
+### Popups
+
+- The HTML markup for a popup has been changed to make it easier to style with CSS.
+  The new structure is:
+
+  ```
+  <div class="up-popup">
+    <div class="up-popup-content">
+      Fragment content here
+    </div>
+  </div>
+  ```
+- The default CSS styles for `.up-popup` has been changed. If you have customized popup styles,
+  you should check if your modifications still work with the new defaults.
+- Popups now update their position when the screen is resized.
+- Popups now follow scrolling when placed within [viewports](/up.viewport) other than the main document.
+- The `[up-position]` attribute has been split into two attributes `[up-position]` and `[up-align]`.
+  Similarly the `{ position }` option has been split into two options `{ position }` and `{ align }`:
+  - `{ position }` defines on which side of the opening element the popup is attached. Valid values are `'top'`, `'right'`, `'bottom'` and `'left'`.
+  - `{ align }` defines the alignment of the popup along its side.
+  - When the popup's `{ position }` is `'top'` or `'bottom'`, valid `{ align }` values are `'left'`, `center'` and `'right'`.
+  - When the popup's `{ position }` is `'left'` or `'right'`, valid `{ align }` values are `top'`, `center'` and `bottom'`.
+- New experimental function `up.popup.sync()`. It forces the popup to update its position when a
+  layout change is not detected automatically.
+- popup elements are now appended to the respective viewport of the anchor element.
+  They were previously always appended to the end of the `<body>`.
+- The events `up:popup:open`,`up:popup:opened`, `up:popup:close` and `up:popup:closed` have an `{ anchor }` property.
+  It references the element that the popup was [attached](/up.popup.attach()) to.
+
+
+### Tooltips
+
+- The HTML markup for a popup has been changed to make it easier to style with CSS.
+  The new structure is:
+
+  ```
+  <div class="up-tooltip">
+    <div class="up-tooltip-content">
+      Tooltip text here
+    </div>
+  </div>
+  ```
+- The default CSS styles for `.up-tooltip` have been changed. If you have customized tooltip styles,
+  you should check if your modifications still work with the new defaults.
+- Tooltips now update their position when the screen is resized.
+- Tooltips now follow scrolling when placed within [viewports](/up.viewport) other than the main document.
+- The `[up-position]` attribute has been split into two attributes `[up-position]` and `[up-align]`. Similarly the `{ position }` option has been split into two options `{ position }` and `{ align }`:
+  - `{ position }` defines on which side of the opening element the popup is attached. Valid values are `'top'`, `'right'`, `'bottom'` and `'left'`.
+  - `{ align }` defines the alignment of the popup along its side.
+  - When the tooltip's `{ position }` is `'top'` or `'bottom'`, valid `{ align }` values are `'left'`, `center'` and `'right'`.
+  - When the tooltip's `{ position }` is `'left'` or `'right'`, valid `{ align }` values are `top'`, `center'` and `bottom'`.
+- New experimental function `up.tooltip.sync()`. It forces the popup to update its position when a
+  layout change is not detected automatically.
+- Tooltip elements are now appended to the respective viewport of the anchor element.
+  They were previously always appended to the end of the `<body>`.
+
+
+### Ruby on Rails integration
+
+- Unpoly is now compatible with the jQuery-less UJS adapter (now [part of Action View](https://github.com/rails/rails/tree/master/actionview/app/assets/javascripts)).
+
+
+### AJAX acceleration
+
+- The properties for the `up:link:preload` event have been renamed.
+
+
+### Modal dialogs
+
+- Opening/closing a modal will now manipulate the `{ overflow-y }` style on the same element
+  that was chosen by the CSS author ([nasty details](https://makandracards.com/makandra/55801-does-html-or-body-scroll-the-page)).
+
+
+### Various
+
+- Renamed some files so they won't be blocked by over-eager ad blockers on developer PCs.
+- Deprecation warnings are only printed once per environment.
+
+
 
 
 0.57.0

data/Gemfile.lock

@@ -4,8 +4,8 @@ GEM
     coffee-script (2.4.1)
       coffee-script-source
       execjs
-    coffee-script-source (1.9.1.1)
-    execjs (2.5.2)
+    coffee-script-source (1.12.2)
+    execjs (2.7.0)
     hike (1.2.3)
     json (1.8.2)
     libv8 (3.16.14.11)
@@ -40,3 +40,6 @@ DEPENDENCIES
   sprockets-standalone
   therubyracer
   uglifier
+
+BUNDLED WITH
+   1.16.1

data/README.md

@@ -52,7 +52,7 @@ To run RSpec tests for the `unpoly-rails` gem:
 
 We are currently feeding four release channels:
 
-- Manual download from Github
+- Manual download from GitHub
 - npm
 - Bower (which is based on Git and version tags)
 - Rubygems (as the `unpoly-rails` gem)

data/README_RAILS.md

@@ -110,7 +110,7 @@ Development
 
 ### Before you make a PR
 
-Before you make a PR, please have some discussion about the proposed change by [opening an issue on Github](https://github.com/unpoly/unpoly/issues/new).
+Before you make a PR, please have some discussion about the proposed change by [opening an issue on GitHub](https://github.com/unpoly/unpoly/issues/new).
 
 ### Running tests
 

data/Rakefile

@@ -41,6 +41,15 @@ Sprockets::Standalone::RakeTask.new(:minified_assets) do |task, sprockets|
 end
 
 namespace :publish do
+  task :confirm do
+    puts "Are you ready to publish a new Unpoly version to all release channels? [y/N] "
+    reply = STDIN.gets.strip.downcase
+    unless reply == 'y'
+      puts "Aborted"
+      exit
+    end
+  end
+
   desc 'Build release artifacts'
   task :build do
     ENV['JS_KNIFE'] = nil
@@ -99,7 +108,7 @@ namespace :publish do
   end
 
   desc 'Build artifacts, push to git and release to package managers'
-  task :all => [:build, :commit, :release, :remind_to_update_site] do
+  task :all => [:confirm, :build, :commit, :release, :remind_to_update_site] do
   end
 
 end