[Rails-core] Re: Deprecation warnings after changing to Rails 5/beta1

2015-12-20 Thread Kir Shatrov
That's right: Rails 5.0.0beta1 is using the edge version of Turbolinks. Right now edge Turbolinks are not released on Rubygems, but we will definitely push the new version before Rails 5 final. On Saturday, December 19, 2015 at 10:56:25 AM UTC+2, Al wrote: > > Wanted to document this somewhere. >

[Rails-core] Re: Deprecation warnings after changing to Rails 5/beta1

2015-12-20 Thread Kir Shatrov
+ https://github.com/rails/turbolinks/issues/628 On Sunday, December 20, 2015 at 11:49:13 AM UTC+2, Kir Shatrov wrote: > > That's right: Rails 5.0.0beta1 is using the edge version of Turbolinks. > Right now edge Turbolinks are not released on Rubygems, but we will > definitely push the new versio

[Rails-core] Re: Deprecation warnings after changing to Rails 5/beta1

2015-12-20 Thread Al
Kir, Saw #628, but did not assume 3.0.0 was the next turbolink release after 2.5.3. Now I understand. Thanks, Al On Sunday, December 20, 2015 at 4:51:01 AM UTC-5, Kir Shatrov wrote: > > + https://github.com/rails/turbolinks/issues/628 > > On Sunday, December 20, 2015 at 11:49:13 AM UTC+2, Kir S

[Rails-core] ActionCable using Postgres listen/notify

2015-12-20 Thread Sean Linsley
Hi there, The contributing guide suggests to write up feature requests on this out-of-the-way mailing list, and I couldn't find a ticket or a blog post around using Postgres listen/notify with ActionCable (in fact the only thing I could find was: https://twitter.com/guilleiguaran/status/590526

Re: [Rails-core] ActionCable using Postgres listen/notify

2015-12-20 Thread richard schneeman
On a plane right now and can't really dig in but the subject interests me. If you're interested I have an ultra simple gem that uses AR for listen/notify in PG https://github.com/schneems/hey_you --- Richard Schneeman http://www.schneems.com On Sun, Dec 20, 2015 at 1:15 PM -0800, "Sean Linsl

Re: [Rails-core] ActionCable using Postgres listen/notify

2015-12-20 Thread Sean Linsley
Hey Richard, in the time between when this post was submitted and when it was approved for the mailing list, I made some progress reading through the existing implementation. There are some notes on the Twitter thread: https://twitter.com/seanlinsley/status/678654835982524416