Skip to content

Releases: Shopify/turbograft

v0.1.12

23 Jan 21:59
Compare
Choose a tag to compare

Changes

  • (#64) Enable turbograft on ios chrome.

v0.1.11

22 Jan 22:28
Compare
Choose a tag to compare

Changes

  • (#60) fixes autofocus not working.

v0.1.10

20 Jan 19:28
Compare
Choose a tag to compare

Changes

  • (#61) page:before-partial-replace will now only fire once. The data returned refers to a list of nodes that are marked to be replaced. page:load event data will return a list of nodes actually replaced (previously, some stale or detached nodes were returned here)

v0.1.9

15 Jan 18:39
Compare
Choose a tag to compare

Changes

  • (#58) Fixes a bug with refresh-always (present from 0.1.5 through 0.1.8) that would effectively have the consequence of making nodes marked with this attribute disappear

v0.1.8

15 Jan 18:38
Compare
Choose a tag to compare

Changes

  • (#59) Fixes a bug where _method was not properly sent with tg-remote and multipart forms

v0.1.7

14 Jan 15:02
Compare
Choose a tag to compare

Changes

  • (#57) Fixed up the event.data in page:load event to properly contain a list of new nodes added into the DOM. As of 0.1.5, 0.1.6, this event did not contain the nodes as it should have.

v0.1.6

13 Jan 15:31
Compare
Choose a tag to compare

Changes

  • #56: Don't set session variable if redirect header is not set.

v0.1.5

09 Jan 20:20
Compare
Choose a tag to compare

Changes

  • #53: With the tg-static attribute decorating a node, we can make sure that this node is not replaced during a fullpage refresh. Though, if you were to refresh the page at a higher level -- e.g., refreshing an ancestor of the tg-static, the static aspect is no longer obeyed and it is replaced.
  • #53: Fixed up refresh-always key to literally always refresh the node annotated. Previously, it was refreshing only if you did a Page.refresh(onlyKeys: [...]) with some keys, which was a very misleading name for something called refresh-always

v0.1.4

15 Dec 16:01
Compare
Choose a tag to compare

Changes

  • Now we properly submit the right HTTP request type when using tg-remote. E.g., when using PATCH, we add _method=PATCH to the payload of the form if not already present. Rails interprets these and considers them to be the true HTTP method type, even if the actual HTTP method submitted by the browser is a POST. Prior releases would have seen incorrect behaviour when trying to use tg-remote with methods other than POST
  • tg-remote-norefresh attribute (no value required) on a node with tg-remote will now prevent Page.refresh from firing entirely. This is useful for situations where you are handling state entirely in the client and want to perform a method and have 0 side effects.

from #51

v0.1.3

10 Dec 17:18
Compare
Choose a tag to compare

Changes

  • Properly grab the CSRF token from the meta[name='csrf-token'] element; was previously attempting to grab it from meta[name='X-CSRF-Token'], a grievous mistake (#50)
  • Properly bubble the click events for tg-remote on <a> and <button> elements that had DOM nodes inside of them (#49)