Tutorial¶

Hello World¶

Lets build a simple app to get familiar with Superglue.

Start with the usual¶

Add a route and a controller to an app that followed the installation steps.

Info

The installation steps will include a layout application.json.props that's implicitly used in this tutorial.

routes.rbgreet_controller.rb

in app/config/routes.rb

resource :greet, only: :show

in app/controllers/greet_controller.rb

class GreetController < ApplicationController
  def show
  end
end

Add the views¶

Next lets add the following views. Here we're splitting the usual show.html.erb into 3 parts:

app/views/greet/show.json.props
app/views/greet/show.js
app/views/greet/show.html.erb

1. show.json.props2. show.js3. show.html.erb

If you've used Jbuidler, this should look familiar. Here, we're using props_template, a Jbuilder inspired templating DSL built for superglue.

Info

Shape the page to how you would visually organize your components. Superglue encourages you to shape json responses to include both data AND presentation.

json.body do
  json.greet "Hello world"
end

json.footer "Made with hearts"

This is the page component that will recieve the result of show.json.props.

import React from 'react'

export default function GreetShow({
  body,
  footer
}) {
  const {greet} = body

  return (
    <h1>{greet}</h1>
    <span>{footer}</span>
  )
}

Info

This file is usually generated by a scaffold and stays exactly the same regardless if its index.html.erb, show.html.erb, edit.html.erb, etc.

<% initial_state = controller.render_to_string(formats: [:json], locals: local_assigns, layout: true) %>

<script type="text/javascript">
  window.SUPERGLUE_INITIAL_PAGE_STATE=<%= initial_state.html_safe %>;<%# erblint:disable ErbSafety %>
</script>

<div id="app"></div>

This file renders show.json.props, injects it globally as the initial state to be picked up by Superglue on the browser.

Connect the dots¶

The json payload that gets rendered into show.html.erb also contains information about the template it rendered from the componentIdentifier.

Info

If you do not knowing what the componentIdentifier of a page is, you can go to the json version of the page on your browser to see what gets rendered. In our case: http://localhost:3000/greet.json

We're going to use the componentIdentifier to tie show.json.props to show.js so superglue knows which component to render with which response by modifying app/javascript/page_to_page_mapping.js.

1. Example greet.json2. page_to_page_mapping.js

The layout for show.json.props is located at app/views/layouts/application.json.props. It conforms to superglue's payload response, and uses the active_template_virtual_path as the componentIdentifier.

{
  data: {
    body: {
      greet: "Hello world"
    }
    footer: "Made with hearts"
  },
  componentIdentifier: "greet/show",
  ...
}

import GreetShow from '../views/greet/show'

export const pageIdentifierToPageComponent = {
  'greet/show': GreetShow,
};

Finish¶

Run a rails server and go to http://localhost:3000/greet.

Productivity¶

That was quite an amount of steps to get to a Hello World. For simple functionality it's not immediately obvious where Superglue fits, but for medium complexity and beyond, Superglue shines where it can be clunky for tools like Turbo, Hotwire and friends.

Let's add some complexity to the previous sample.

Digging for content¶

But first! A quick dive into props_template. Click on the tabs to see what happens when @path changes for the example below.

json.data(search: @path) do
  json.body do
    json.chart do
      sleep 10
      json.header "Sales"
    end

    json.user do
      json.name "John"
    end
  end

  json.footer do
    json.year "2003"
  end
end

json.componentIdentifier "someId"

datadata.bodydata.body.userdata.footer

When @path = ['data']. There's a 10 second sleep, and the output will be:

{
  data: {
    body: {
      chart: {
        header: "Sales"
      },
      user: {
        name: "John"
      }
    },
    footer: {
      year: "2003"
    }
  },
  componentIdentifier: "someId"
}

When @path = ['data', 'body']. There's a 10 second sleep, and the output will be:

{
  data: {
    chart: {
      header: "Sales"
    },
    user: {
      name: "John"
    }
  },
  componentIdentifier: "someId"
}

When @path = ['data', 'body', 'user'], there is no wait, and the json will be:

{
  data: {
    name: "john"
  },
  componentIdentifier: "someId"
}

When @path = ['data', 'year'], there is no wait, and the json will be:

{
  data: {
    year: "2003"
  },
  componentIdentifier: "someId"
}

Continuing where we last left off¶

Lets add a 5 second sleep to show.json.props so ever user is waiting 5 seconds for every page load.

show.json.props

json.body do
  sleep 5
  json.greet "Hello world"
end

json.footer "Made with hearts"

How should we improve the user experience?

Load the content later (Manual deferment)¶

What if we add a link on the page that would load the greeting async? Sounds like a good start, lets do that. We'll use defer: :manual to tell props_template to skip over the block.

show.json.propsoutputshow.js

json.body(defer: :manual)
  sleep 5
  json.greet "Hello world"
end

json.footer "Made with hearts"

Adding defer: :manual will replace the contents with an empty object.

{
  data: {
    body: {},
    footer: "Made with hearts"
  },
  componentIdentifier: "greet/show",
  ...
}

We'll also have to handle the case when there is no greeting.

Info

We'll improve on this approach. The defer option can specify a fallback.

import React from 'react'

export default function GreetShow({
  body,
  footer,
  loadGreetPath
}) {
  const {greet} = body

  return (
    <h1>{greet || "Waiting for greet"}</h1>
    <a href={loadGreetPath} data-sg-remote>Load Greet</a>
    <span>{footer}</span>
  )
}

Add a link¶

Now when the user lands on the page, we're no longer waiting 5 seconds. Lets add a link that will dig for the missing content to replace "Waiting for greet".

show.json.propsshow.js

Add a url for the href link with props_at param. This is used on the application.json.props layout that instructs PropsTemplate to dig.

json.body(defer: :manual)
  sleep 5
  json.greet "Hello world"
end

json.loadGreetPath greet_path(props_at: "data.body")

json.footer "Made with hearts"

Superglue embraces Unobtrusive Javascript. Add a data-sg-remote to any link, and superglue will take care of making the fetch call.

import React from 'react'

export default function GreetShow({
  body,
  footer,
  loadGreetPath
}) {
  const {greet} = body

  return (
    <h1>{greet || "Waiting for greet"}</h1>
    <a href={loadGreetPath} data-sg-remote>Greet!</a>
    <span>{footer}</span>
  )
}

`show.js` alternative¶

This version does the same thing. Every page component receives a remote and visit thunk.

import React from 'react'

export default function GreetShow({
  body,
  remote,
  footer,
  loadGreetPath
}) {
  const {greet} = body
  const handleClick = (e) => {
    e.preventDefault()
    remote(loadGreetPath)
  }

  return (
    <h1>{greet || "Waiting for greet"}</h1>
    <a href={loadGreetPath} onClick={handleClick}>Greet!</a>
    <span>{footer}</span>
  )
}

Finish¶

And that's it. Now you have a button that will load content in async fashion, but how does it all work? Lets take a look at loadGreetPath

/greet?props_at=data.greet

The shape of show.json.props is exactly the same as what is stored in the redux store on pages["/greet"]. With a single keypath on props_at we grabbed the content at data.greet from show.json.props AND stored it on data.greet on pages["/greet"].

Now that's productive!

Improvements¶

In practice, there's a far simpler solution: defer: :auto, which would do all of the above without a button.

show.json.propsshow.js

The only change needed would be to use the :auto option with a placeholder. The response would tell Superglue to:

Save the page (with the placeholder)
Look for any deferred nodes
Automatically create a remote request for the missing node

json.body(defer: [:auto, placeholder: { greet: "Waiting for Greet"})
  sleep 5
  json.greet "Hello world"
end

json.footer "Made with hearts"

No changes to the original show.js component. We don't even have to create a conditional, the initial page response will contain a placeholder.

import React from 'react'

export default function GreetShow({
  body,
  footer
}) {
  const {greet} = body

  return (
    <h1>{greet}</h1>
    <span>{footer}</span>
  )
}

Tutorial¶

Hello World¶

Start with the usual¶

Add the views¶

Connect the dots¶

Finish¶

Productivity¶

Digging for content¶

Continuing where we last left off¶

Load the content later (Manual deferment)¶

Add a link¶

show.js alternative¶

Finish¶

Improvements¶

`show.js` alternative¶