Alpine.js for Ruby on Rails Developers: Simplifying Front End Development
alexsinelnikov.blog
Alpine.js for Ruby on Rails Developers: Simplifying Front End Development
1–10 of 10 posts
Re: Alpine.js for Ruby on Rails Developers: Simplifying Front End Development
#2[deleted]
Re: Alpine.js for Ruby on Rails Developers: Simplifying Front End Development
#3[deleted]
Re: Alpine.js for Ruby on Rails Developers: Simplifying Front End Development
#4[deleted]
Re: Alpine.js for Ruby on Rails Developers: Simplifying Front End Development
#5But how would Alpine communicate with the Rails backend? Do I have to manually map the routes url between FE and BE?
Re: Alpine.js for Ruby on Rails Developers: Simplifying Front End Development
#6But how would Alpine communicate with the Rails backend? Do I have to manually map the routes url between FE and BE?
It doesn't help to share state between the front and the backend. What apline.js really excels at is managing state on the frontend itself, especially for UI. For example, if you need to click on one thing that shows another thing, or you need to swap out ui elements it helps to make that easier.
For communicating the backend through using an api, or issuing async get/post or form submissions that is done pretty much the same as you would do it using html or javascript.
Re: Alpine.js for Ruby on Rails Developers: Simplifying Front End Development
#7As long as it passes jslint.com I will support this.
Re: Alpine.js for Ruby on Rails Developers: Simplifying Front End Development
#8But how would Alpine communicate with the Rails backend? Do I have to manually map the routes url between FE and BE?
It doesn't help to share state between the front and the backend. What apline.js really excels at is managing state on the frontend itself, especially for UI. For example, if you need to click on one thing that shows another thing, or you need to swap out ui elements it helps to make that easier. For communicating the backend through using an api, or issuing async get/post or form submissions that is done pretty much…
Yes, and Alpine would often be paired with HTMX to handle client/server interactions.
And Rails has their own flavor of this with Hotwire/Turbo.
Re: Alpine.js for Ruby on Rails Developers: Simplifying Front End Development
#9But how would Alpine communicate with the Rails backend? Do I have to manually map the routes url between FE and BE?
You can use https://alpine-ajax.js.org for this, or Alpine can work as an alternative to Stimulus.js in the Hotwire stack.
Re: Alpine.js for Ruby on Rails Developers: Simplifying Front End Development
#10But how would Alpine communicate with the Rails backend? Do I have to manually map the routes url between FE and BE?
Yeah as folks said below - Rails provides data to alpine, and alpine manages state based on initial value. But you can do regular XHR requests from alpine too, since it has regular functions which you can call