TurboComponent

This project explores the idea of components not only in terms of view, like view_component or cells, but it also includes server actions required for the component.

I part from the codebase of pagelet_rails and take advantage of turbo_rails to explore this idea.

Please do not use it. It is a work in progress.

First of all, install turbo-rails.

Add 'turbo_component', '0.1.0.pre' to the Gemfile.

Since this project is in an exploratory phase, you would like to use the master branch to get the last changes.

gem 'turbo_component', git: 'https://github.com/ceritium/turbo_component.git'

Add TurboComponent::Router.load_routes!(self) to the routes.rb

Generate a turbo component:

 rails g turbo_component Sidebar

Use it somewhere:

<%= turbo_component :sidebar %>

# or...

<%= turbo_component :sidebar, permanent: true, async: true do %>
  loading...
<% end %>

Because turbo_components are small you will have many of them. In order to keep them under control turbo_componets provides helpers.

You can define get, post, put, patch and delete inside your component controller as following:

post :toggle_categories
def toggle_categories
  session[:show_categories] = !session[:show_categories]
  show
  render :show
end

There is also the display method to define the default action of your turbo_component:

display :show
def show
  @categories = Category.all
  @categories = @categories.where('name like :name', name: "%#{params[:name]}%") if params[:name]
end

turbo_component accepts all the parameters of turbo_frame_tag plus some additional attributes:

• async: Allow render it inline or async (powered by turbo_frame). Default false.
• turbo_id: It is used as id on the turbo_frame_tag and for encoding the locals. Default $turbo_component_key, in the example is sidebar.
• locals: Like on render partial: you can pass attributes to the turbo component. In the case of loading it async, the locals are serialized and encrypted.

Example:

<%= turbo_component :vote_author, async: true, locals: { author: @author } do %>
  loading...
<% end %>

There is a rails demo app available: https://github.com/ceritium/turbo_component-demo

• Add more demos and use cases.
• Improve testing.
• Consider view_component as default view system.
• Explore how to deal with broadcast callbacks, I would like to define them inside the turbo component.
• Improve gem setup.
• Refactor, most of this gem is C&P from pagelet and glue code.