vident

Vident

Vident is a collection of gems that help you create flexible & maintainable component libraries for your Rails application.

Vident also provides a neat Ruby DSL to make wiring up Stimulus easier & less error prone in your view components.

ViewComponent and Phlex supported.

Motivation

I love working with Stimulus, but I find manually crafting the data attributes for targets and actions error-prone and tedious. Vident aims to make this process easier and keep me thinking in Ruby.

Vident has been used with ViewComponent and Phlex in production apps for a while now but is still evolving.

I would love to get your feedback and contributions!

Example

The Greeter ViewComponent (that uses Vident):

Consider a component, the GreeterComponent:

# app/components/greeter_component.rb

class GreeterComponent < ::Vident::ViewComponent::Base
  renders_one :trigger, ButtonComponent
end

with ERB as follows:

<%# app/components/greeter_component.html.erb %>

<%# Rendering the `root` element creates a tag which has stimulus `data-*`s, a unique id & other attributes set. %>
<%# The stimulus controller name (identifier) is derived from the component name, and then used to generate the relavent data attribute names. %>

<%= render root named_classes: {
  pre_click: "text-md text-gray-500", # named classes are exposed to Stimulus as `data-<controller>-<name>-class` attributes
  post_click: "text-xl text-blue-700",
  html_options: {class: "py-2"}
} do |greeter| %>
  <%# `greeter` is the root element and exposes methods to generate stimulus targets and actions %>
  <input type="text"
         <%= greeter.as_target(:name) %>
         class="shadow appearance-none border rounded py-2 px-3 text-gray-700 leading-tight focus:outline-none focus:shadow-outline">
  
  <%# Render the slot %>
  <%= trigger %>
  
  <%# you can also use the `target_tag` helper to render targets %>
  <%= greeter.target_tag(
        :span, 
        :output, 
        # Stimulus named classes can be referenced to set class attributes at render time
        class: "ml-4 #{greeter.named_classes(:pre_click)}" 
      ) do %>
    ...
  <% end %>
<% end %>

Now, imagine we render it in a view, and render a ButtonComponent in the trigger slot:

<%= render ::GreeterComponent.new(cta: "Hey!", html_options: {class: "my-4"}) do |greeter| %>
  <%# this component has a slot called `trigger` that renders a `ButtonComponent` (which also uses Vident) %> 
  <% greeter.with_trigger(
       
       # The button component has attributes that are typed
       before_clicked: "Greet",
       after_clicked: "Greeted! Reset?",
       
       # A stimulus action is added to the button that triggers the `greet` action on the greeter stimulus controller.
       # This action will be added to any defined on the button component itself
       actions: [
         greeter.action(:click, :greet),
       ],
       
       # We can also override the default button classes of our component, or set other HTML attributes
       html_options: {
         class: "bg-red-500 hover:bg-red-700"
       }
     ) %>
<% end %>

The output HTML of the above, using Vident, is:

<div class="greeter-component py-2 my-4" 
     data-controller="greeter-component" 
     data-greeter-component-pre-click-class="text-md text-gray-500" 
     data-greeter-component-post-click-class="text-xl text-blue-700" 
     id="greeter-component-1599855-6">
  <input type="text" 
         data-greeter-component-target="name" 
         class="shadow appearance-none border rounded py-2 px-3 text-gray-700 leading-tight focus:outline-none focus:shadow-outline">
  <button class="button-component ml-4 whitespace-no-wrap bg-blue-500 hover:bg-blue-700 text-white font-bold py-2 px-4 rounded bg-red-500 hover:bg-red-700" 
          data-controller="button-component" 
          data-action="click->greeter-component#greet button-component#changeMessage" 
          data-button-component-after-clicked-message="Greeted! Reset?" 
          data-button-component-before-clicked-message="Greet" 
          id="button-component-7799479-7">Hey!</button>
  <!-- you can also use the `target_tag` helper to render targets -->
  <span class="ml-4 text-md text-gray-500" 
        data-greeter-component-target="output">
    ...
  </span>
</div>

To see this example in more detail, see the vident-typed-view_component test dummy app.

Vident is a collection of gems

The core gems are:

• vident to get the base functionality
• vident-typed to optionally define typed attributes for your view components

Gems that provide support for ViewComponent and Phlex:

• vident-view_component for using with ViewComponent and untyped attributes
• vident-typed-view_component for using with ViewComponent and typed attributes
• vident-phlex for using with Phlex and untyped attributes
• vident-typed-phlex for using with Phlex and typed attributes

There is also:

• vident-typed-minitest to get some test helpers for typed attributes (auto generates inputs to test attributes)
• vident-better_html to support better_html if you use it in your Rails app
• vident-tailwind to get all the benefits of the amazing tailwind_merge.

Things still to do...

This is a work in progress. Here's what's left to do for first release:

• Iterate on the interfaces and functionality
• Add tests
• Make the gem more configurable to fit more use cases
• Create an example library of a few components for some design system
  • Create a demo app with lookbook and those components
• Add more documentation

About Vident

What does Vident provide?

• Base classes for your ViewComponent components or Phlex components that provides a helper to create the all important 'root' element component (can be used with templated or template-less components).

• implementations of these root components for creating the 'root' element in your view components. Similar to Primer::BaseComponent but exposes a simple API for configuring and adding Stimulus controllers, targets and actions. The root component also handles deduplication of classes, creating a unique ID, setting the element tag type, handling possible overrides set at the render site, and determining stimulus controller identifiers etc

• a way to define attributes for your components, either typed or untyped, with default values and optional validation.

Various utilities

Such as...

• for Taiwind users, a mixin for your vident component which uses tailwind_merge to merge TailwindCSS classes so you can easily override classes when rendering a component.
• a mixin for your Vident Components which provides a #cache_key method that can be used to generate a cache key for fragment caching or etag generation.
• a test helper for your typed Vident ViewComponents which can be used to generate good and bad attribute/params/inputs

All the Features...

• use Vident with ViewComponent or Phlex or your own view component system
• A helper to create the root HTML element for your component, which then handles creation of attributes.
• Component arguments are defined using the attribute method which allows you to define default values, (optionally) types and if blank or nil values should be allowed.
• You can use the same component in multiple contexts and configure the root element differently in each context by passing options to the component when instantiating it.
• Stimulus support is built in and sets a default controller name based on the component name.
• Stimulus actions, targets and classes can be setup using a simple DSL to avoid hand crafting the data attributes.
• Since data attribute names are generated from the component class name, you can rename easily refactor and move components without having to update the data attributes in your views.
• Components are rendered with useful class names and IDs to make debugging easier (autogenerated IDs are 'random' but deterministic so they are the same each time a given view is rendered to avoid content changing/Etag changing).
• (experimental) Support for fragment caching of components (Vident::Caching and Vident::<ViewComponent | Phlex>::Caching... implementation has caveats)
• (experimental) A test helper to make testing components easier by utilising type information from the component arguments to render automatically configured good and bad examples of the component.
• (experimental) support for better_html

Installation

This gem (vident) provides only base functionality but there are a number of gems that provide additional functionality or an "out of the box" experience.

It's a "pick your own adventure" approach. You decide what frameworks and features you want to use and add the gems as needed.

First, add this line to your application's Gemfile:

gem 'vident'

Then go on to choose the gems you want to use:

Q1. Do you want to use ViewComponent or Phlex for your view components?

For ViewComponent use:

• vident-view_component

For Phlex use:

• vident-phlex

Note: you can also use both in the same app.

For example, if you want to use ViewComponent and Phlex in the same app, you might end up with:

gem 'vident'
gem 'vident-view_component'
gem 'vident-phlex'

Q2. Do you want to build components where the attributes have runtime type checking (powered by dry-types)?

If yes, then add vident-typed to your Gemfile:

gem 'vident-typed'

and then use the relavent *-typed-* gems for your chosen view component system:

• use vident-typed-view_component
• and/or vident-typed-phlex

Note you must also include the gem for the view component system you are using.

For example, for ViewComponent, you might end up with:

gem 'vident'
gem 'vident-view_component'
gem 'vident-typed'
gem 'vident-typed-view_component'

Q3. Do you use or want to use BetterHTML in your Rails project?

If yes, then include vident-better_html in your Gemfile alongside better_html and your vident gems of choice.

...
gem 'better_html'
gem 'vident-better_html'

Note that vident-better_html automatically enables better_html support in Vident root components.

Q4. Do you use or want to use TailwindCSS?

If yes, then consider adding vident-tailwind to your Gemfile alongside your vident gems of choice.

...
gem 'vident-tailwind'

When creating your components you can then include Vident::Tailwind to get all the benefits of the amazing tailwind_merge.

Q5. Did none of the above gems suit your needs?

You can always just use base vident gems and then roll your own solutions:

• vident to get the base functionality to mix with your own view component system
• vident-typed to define typed attributes for your own view component system

Documentation

See the docs directory and visit the individual gem pages for more information.

Development

After checking out the repo, run bin/setup to install dependencies. Then, run rake test to run the tests. You can also run bin/console for an interactive prompt that will allow you to experiment.

To install this gem onto your local machine, run bundle exec rake install. To release a new version, update the version number in version.rb, and then run bundle exec rake release, which will create a git tag for the version, push git commits and the created tag, and push the .gem file to rubygems.org.

Contributing

Bug reports and pull requests are welcome on GitHub at https://github.com/stevegeek/vident. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the code of conduct.

License

The gem is available as open source under the terms of the MIT License.

Code of Conduct

Everyone interacting in the Vident project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the code of conduct.