Brian Knoles

No, no `:remote => true` option on the links. I set `updateHash: false` in the easytabs options and now the load only happens once. It seems that easytabs selects the...

It triggers twice when `updateHash: true` is in the options, according to the console

The source for the page only shows it included once. I searched through the other js files in the stack to make sure that they don't have the hashchange defined,...

I don't have the address plugin... here's the list of what I have jquery.js jquery_ujs.js jquery.purr.js best_in_place.js jquery.jeditable.mini.js jquery.jeditable.checkbox.js on_the_spot_code.js on_the_spot.js jquery-ui-1.8.16.custom.min.js jquery.ba-hashchange.js jquery.easytabs.js jquery.iframe-transport.js jquery.remotipart.js jquery.spin.js mainpage.js spin.js myapplication.js...

haha yea you've made my life pretty easy. I'm going to just turn off the updatehash. If I decide i really need the back button functionality, I'll revisit. Thanks for...

No live demo right now... Everything is running on my local machine

Hey @seanders have you tried this with an Inertia app? https://github.com/inertiajs/inertia-rails/blob/master/lib/inertia_rails/renderer.rb#L25 Under the hood, the gem renders the props as locals within a Rails template on the initial page load,...

Yea, great discussion here. I think we're in need of a refactor away from storing shared data in a variable on the module. @clemens comment (echoed by @buhrmi ): >...

Actually, I think storing per-request data in a `class_attribute` has issues also. It's still a global variable; it's just scoped to the controller instead of the library. As of today,...

Thanks for the link @buhrmi I'd definitely prefer to keep the existing API if we can feel confident that the `class_attribute` changes are safe. A breaking change is always a...