You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm looking to stop building my apps using Xamarin and found Turbolinks which is what BaseCamp is using to do their mobile app development. I like not having two different codebases so then it leads me to this project but looks like the last commit was 2018 and it references the Turbolinks Classic.
I'm still reading up but wanted to know if this is still the best way to do this? or is there something new in the past couple years?
The text was updated successfully, but these errors were encountered:
It seems to me it uses turbolinks 5. There is a PR for that too.
What I was wondering is: what is the need for a Middleware? According to turbolinks documentation it shouldn't require server cooperation
You still need some server support if you want to handle redirects, which is what the ruby gem does for rails.
I havn't worked on this for a very long time, but this middleware was not a lot of lines of code, its likely it could be augmented to work with turbolinks 5, it appears turbolinks classic and 5 have slightly different http headers they use to do redirects and what not.
I'm looking to stop building my apps using Xamarin and found Turbolinks which is what BaseCamp is using to do their mobile app development. I like not having two different codebases so then it leads me to this project but looks like the last commit was 2018 and it references the Turbolinks Classic.
I'm still reading up but wanted to know if this is still the best way to do this? or is there something new in the past couple years?
The text was updated successfully, but these errors were encountered: