KO | EN

GitLite

Minimalist Open Source Repository Search Engine

gitlite — search

#dsh #dsh-plugin #ai-agent #developer-tools #codex #typescript #cli #deepseek-harness #claude-code #ai-agents #mcp #rust

props_template

★ 200 Open GitHub ↗

A very fast json builder for Rails

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# PropsTemplate

PropsTemplate is a direct-to-Oj, JBuilder-like DSL for building JSON. It has
support for Russian-Doll caching, layouts, and can be queried by giving the
root a key path.

[![Build
Status](https://circleci.com/gh/thoughtbot/props_template.svg?style=shield)](https://circleci.com/gh/thoughtbot/props_template)

It's fast.

PropsTemplate bypasses the steps of hash building and serializing
that other libraries perform by using Oj's `StringWriter` in `rails` mode.

![benchmarks](https://raw.githubusercontent.com/thoughtbot/props_template/main/docs/benchmarks.png)

It's really fast.

`props_template` is second only to `panko` while being feature packed. The
`Props::Base` [class](./lib/props_template/base.rb) that be used standalone
is the fastest among all JSON serializers. Results derived from [alba benchmarks](https://github.com/thoughtbot/alba/tree/main/benchmark).

```
    props_base_class:     1439.9 i/s
               panko:     1287.6 i/s - 1.12x  slower
      props_template:      998.8 i/s - 1.44x  slower
       turbostreamer:      912.9 i/s - 1.58x  slower
                alba:      871.0 i/s - 1.65x  slower
         jserializer:      668.7 i/s - 2.15x  slower
alba_with_transformation:      604.2 i/s - 2.38x  slower
              barley:      452.2 i/s - 3.18x  slower
        barley_cache:      441.4 i/s - 3.26x  slower
            jbuilder:      432.6 i/s - 3.33x  slower
     fast_serializer:      390.1 i/s - 3.69x  slower
               rails:      374.1 i/s - 3.85x  slower
                rabl:      310.3 i/s - 4.64x  slower
         blueprinter:      268.4 i/s - 5.36x  slower
       representable:      187.2 i/s - 7.69x  slower
          simple_ams:      124.5 i/s - 11.57x  slower
                 ams:       41.5 i/s - 34.67x  slower
         alba_inline:       10.9 i/s - 131.64x  slower

Gem versions:
active_model_serializers: 0.10.16
alba: 3.10.0
barley: 0.9.0
blueprinter: 1.2.1
jbuilder: 2.14.1
jserializer: 0.2.1
panko_serializer: 0.8.4
rabl: 0.17.0
representable: 3.2.0
simple_ams: 0.2.6
turbostreamer: 1.11.0

Ruby version: 3.4.8
Apple M4 Pro
```

Caching is fast too.

While other libraries spend time unmarshaling,
merging hashes, and serializing to JSON; PropsTemplate simply takes
the cached string and uses Oj's [push_json](http://www.ohler.com/oj/doc/Oj/StringWriter.html#push_json-instance_method).

## Example:

PropsTemplate is very similar to JBuilder, and selectively retains some
conveniences and magic.

```ruby
json.flash flash.to_h

json.menu do
  json.currentUser do
    json.email current_user.email
    json.avatar current_user.avatar
    json.inbox current_user.messages.count
  end
end

json.dashboard(with.defer(:auto)) do
  sleep 5
  json.complexPostMetric 500
end

json.posts do
  page_num = params[:page_num]
  paged_posts = @posts.page(page_num).per(20)

json.list do
    json.array! paged_posts, with.id_key(:id) do |post|
      json.id post.id
      json.description post.description
      json.commentsCount post.comments.count
      json.editPath edit_post_path(post)
    end
  end

json.paginationPath posts_path
  json.current pagedPosts.current_page
  json.total @posts.count
end

json.footer with.partial('shared/footer')
```

## Installation

```
gem 'props_template'
```

and run `bundle`.

Optionally add the [core ext](#array-core-extension) to an initializer if you
want to [dig](#digging) into your templates.

```ruby
require 'props_template/core_ext'
```

And create a file in your `app/views` folder like so:

```ruby
# app/views/posts/index.json.props

json.greetings "hello world"
```

You can also add a [layout](#layouts).

## API

### json.set! or json.\<your key here\>

Defines the attribute or structure. All keys are not formatted by default. See [Change Key Format](#change-key-format) to change this behavior.

```ruby
json.set! :authorDetails, with.some_option do
  json.set! :firstName, 'David'
end

# or

json.authorDetails, with.some_option do
  json.firstName 'David'
end

# or with hash options

json.authorDetails, {...options} do
  json.firstName 'David'
end

# => {"authorDetails": { "firstName": "David" }}
```

The inline form defines key and value

```ruby

json.set! :firstName, 'David'

# or

json.firstName 'David'

# => { "firstName": "David" }

# or

json.postDetails with.partial("blog_post")
```

The block form defines key and structure

```ruby
json.set! :details do
  # ...
end

json.details do
  # ...
end
```

The difference between the block form and inline form is

1. Passing options as a [hash](#hash-options) is only available for the
block form (also called an internal node)
2. The inline form is considered a leaf node, if you need features like
partials you may use [options](#options) objects only.
3. Only internal nodes may dug for [digging](#digging)

### json.extract!
Extracts attributes from object or hash in 1 line

```ruby
# without extract!
json.id user.id
json.email user.email
json.firstName user.first_name

# with extract!
json.extract! user, :id, :email, :first_name

# => {"id" => 1, "email" => "email@gmail.com", "first_name" => "user"}

# with extract! with key transformation
json.extract! user, :id, [:first_name, :firstName], [:last_name, :lastName]

# => {"id" => 1, "firstName" => "user", "lastName" => "last"}
```

The inline form defines object and attributes

### json.array!
Generates an array of json objects.

```ruby
collection = [ {name: 'john'}, {name: 'jim'} ]

json.details do
  json.array! collection, with.some_option do |person|
    json.firstName person[:name]
  end
end

# => {"details": [{"firstName": 'john'}, {"firstName": 'jim'} ]}
```

To support [digging](#digging), any list passed
to `array!` MUST implement `member_at(index)` and `member_by(attr, value)`.

For example, if you were using a delegate:

```ruby
class ObjectCollection < SimpleDelegator
  def member_at(index)
    at(index)
  end

def member_by(attr, val)
    find do |ele|
      ele[attr] == val
    end
  end
end
```

Then in your template:

```ruby
data = ObjectCollection.new([
  {id: 1, name: 'foo'},
  {id: 2, name: 'bar'}
])

json.array! data do
  # ...
end
```

Similarly for ActiveRecord:

```ruby
class ApplicationRecord < ActiveRecord::Base
  def self.member_at(index)
    offset(index).limit(1).first
  end

def self.member_by(attr, value)
    find_by(Hash[attr, val])
  end
end
```

Then in your template:

```ruby
json.array! Post.all do
  # ...
end
```

#### **Array core extension**

For convenience, PropsTemplate includes a core\_ext that adds these methods to
`Array`. For example:

```ruby
require 'props_template/core_ext'
data = [
  {id: 1, name: 'foo'},
  {id: 2, name: 'bar'}
]

json.posts
  json.array! data do
    # ...
  end
end
```

PropsTemplate does not know what the elements are in your collection. The
example above will be fine for [digging](#digging)
by index, but will raise a `NotImplementedError` if you query by attribute. You
may still need to implement `member_by`.

### json.deferred!
Returns all deferred nodes used by the [deferment](#deferment) option.

**Note** This is a [SuperglueJS][1] specific functionality and is used in
`application.json.props` when first running `rails superglue:install:web`

```ruby
json.deferred json.deferred!

# => [{url: '/some_url?props_at=outer.inner', path: 'outer.inner', type: 'auto'}]
```

This method provides metadata about deferred nodes to the frontend ([SuperglueJS][1])
to fetch missing data in a second round trip.

### json.fragments!
Returns all fragment nodes used by the [partial fragments](#partial-fragments)
option.

```ruby json.fragments json.fragments!  ```

**Note** This is a [SuperglueJS][1] specific functionality and is used in
`application.json.props` when first running `rails superglue:install:web`

## Options

PropsTemplate provides a `with` helper to build a `Props::Option` object that enable
functionality such as Partials, Deferments, and Caching

The following are equivalent:

```ruby
json.post(with.partial('blog_post') 
```

```ruby
json.post(Props::Options.new.partial('blog_post') 
```
### Hash options

Previously, a normal hash was supported for internal nodes as long as an empty
block accompanied the option. This option is still supported, but its
recommended to use the `with` option builder.

```ruby
json.post(partial: 'blog_post', locals: {post: @post}) do
end
```

### Partials

Partials are supported. The following will render the file
`views/posts/_blog_posts.json.props`, and set a local variable `post` assigned
with @post, which you can use inside the partial.

```ruby
json.one_post(with.partial("posts/blog_post", locals: {post: @post}))

# or with hash options

json.one_post partial: ["posts/blog_post", locals: {post: @post}] do
end
```

Usage with arrays:

```ruby
# The `as:` option is supported when using `array!`
# Without `as:` option you can use blog_post variable (name is based on partial's name) inside partial

json.posts do
  json.array! @posts, with.partial("posts/blog_post", locals: {foo: 'bar'}, as: 'post')
end
```

Rendering partials without a key is also supported using `json.partial!`, but use
sparingly! `json.partial!` is not optimized for collection rendering and may
cause performance problems. It's best used for things like a shared header or footer.

Do:

```ruby
json.partial! with.partial("header", locals: {user: @user}) 
```

```ruby
json.posts do
  json.array! @posts, with.partial("posts/blog_post", locals: {post: @post})
end
```

Do NOT:

```ruby
@post.each do |post|
  json.partial! partial: "post", locals: {post: @post} do
  end
end
```

### Partial Fragments
**Note** This is a [SuperglueJS][1] specific functionality.

A fragment identifies a partial output across multiple pages. It can be used to
update cross cutting concerns like a header bar.

```ruby
# index.json.props
json.header with.partial("profile").fragment("header")

# _profile.json.props
json.profile do
  json.address do
    json.state "New York City"
  end
end
```

When using fragments with Arrays, the argument **MUST** be a lamda:

```ruby
require 'props_template/core_ext'

json.array! ['foo', 'bar'], with.partial("footer").fragment(->(x){ x == 'foo'})
```

### Caching
Caching is supported on internal nodes only. This limitation is what makes it
possible to for props_template to forgo marshalling/unmarshalling and simply
use [push_json](http://www.ohler.com/oj/doc/Oj/StringWriter.html#push_json-instance_method).

Usage:

```ruby
json.author(with.cache("some_cache_key")) do
  json.firstName "tommy"
end

# or

json.profile(with.cache("cachekey").partial("profile", locals: {foo: 1}))

# or nest it

json.author(with.cache("some_cache_key")) do
  json.address(with.cache("some_other_cache_key")) do
    json.zip 11214
  end
end
```

When used with arrays, PropsTemplate will use `Rails.cache.read_multi`.

```ruby
require 'props_template/core_ext'

opts = with.cache(->(i){ ['a', i] } )

json.array! [4,5], opts do |x|
  json.top "hello" + x.to_s
end

# or on arrays with partials

opts = with.cache(->(d){ ['a', d.id] }).partial("blog_post", as: :blog_post)

json.array! @options, opts do
end
```

### Deferment

You can defer rendering of expensive nodes in your content tree using the
`defer: :manual` option. Behind the scenes PropsTemplates will no-op the block
entirely and replace the value with a placeholder. A common use case would be
tabbed content that does not load until you click the tab.

When your client receives the payload, you may issue a second request to the
same endpoint to fetch any missing nodes. See [digging](#digging)

There is also a `defer: :auto` option that you can use with [SuperglueJS][1]. [SuperglueJS][1]
will use the metadata from `json.deferred!` to issue a `remote` dispatch to fetch
the missing node and immutably graft it at the appropriate keypath in your Redux
store.

Usage:

```ruby
json.dashboard(with.defer(:manual)) do
  sleep 10
  json.someFancyMetric 42
end

# or you can explicitly pass a placeholder

json.dashboard(with.defer(:manual, placeholder: {})) do
  sleep 10
  json.someFancyMetric 42
end
```

A auto option is available:

**Note** This is a [SuperglueJS][1] specific functionality.

```ruby
json.dashboard(with.defer(:auto)) do
  sleep 10
  json.someFancyMetric 42
end
```

Finally in your `application.json.props`:

```ruby
json.defers json.deferred!
```

#### Working with arrays
The default behavior for deferments is to use the index of the collection to
identify an element.

**Note** If you are using this library with [SuperglueJS][1], the `:auto` option will
generate `?props_at=a.b.c.0.title` for `json.deferred!`.

If you wish to use an attribute to identify the element. You must:

1. Use the `:key` option on `json.array!`. This key refers to an attribute on
your collection item, and is used for `defer: :auto` to generate a keypath for
[SuperglueJS][1]. If you are NOT using SuperglueJS, you do not need to do this.

2. Implement `member_at`, on the [collection](#jsonarray). This will be called
by PropsTemplate to when [digging](#digging)

For example:

```ruby
require 'props_template/core_ext'
data = [
  {id: 1, name: 'foo'},
  {id: 2, name: 'bar'}
]

json.posts
  json.array! data, with.id_key(:some_id) do |item|
    # By using :key, props_template will append `json.some_id item.some_id`
    # automatically

json.contact(with.defer(:auto)) do
      json.address '123 example drive'
    end
  end
end
```

If you are using [SuperglueJS][1], it will automatically kick off
`remote(?props_at=posts.some_id=1.contact)` and `remote(?props_at=posts.some_id=2.contact)`.

## Digging

PropsTemplate has the ability to walk the tree you build, skipping execution of
untargeted nodes. This feature is useful for selectively updating your frontend
state.

```ruby
traversal_path = ['data', 'details', 'personal']

json.data(dig: traversal_path) do
  json.details do
    json.employment do
      # ...more stuff
    end

json.personal do
      json.name 'james'
      json.zipCode 91210
    end
  end
end

json.footer do
  # ...
end
```

PropsTemplate will walk depth first, walking only when it finds a matching key,
then executes the associated block, and repeats until the node is found.
The above will output:

```json
{
  "data": {
    "name": 'james',
    "zipCode": 91210
  },
  "footer": {
    ...
  }
}
```

Digging only works with blocks, and will NOT work with Scalars
("leaf" values). For example:

```ruby
traversal_path = ['data', 'details', 'personal', 'name'] # <- not found

json.data(dig: traversal_path) do
  json.details do
    json.personal do
      json.name 'james'
    end
  end
end
```

## Nodes that do not exist

Nodes that are not found will remove the branch where digging was enabled on.

```ruby
traversal_path = ['data', 'details', 'does_not_exist']

json.data(dig: traversal_path) do
  json.details do
    json.personal do
      json.name 'james'
    end
  end
end

json.footer do
  # ...
end
```

The above will render:

```json
{
  "footer": {
    ...
  }
}
```

## Layouts
A single layout is supported. To use, create an `application.json.props` in
`app/views/layouts`. Here's an example:

```ruby
json.data do
  # template runs here.
  _.call(json)
  # NOTE: you can also use `yield json` instead, but prism sees this as
  # a syntax error, so the `_.call(json)` is a workaround.
  # See: https://github.com/thoughtbot/props_template/issues/58
end

json.header do
  json.greeting "Hello"
end

json.footer do
  json.greeting "Hello"
end

json.flash flash.to_h
```

**NOTE** PropsTemplate inverts the usual Rails rendering flow. PropsTemplate
will render Layout first, then the template when `yield json` is used.

### Layouts in API-only Rails apps

If your controllers inherit from `ActionController::API` (typical in API-only Rails apps),
the layout feature won’t work out of the box, because `ActionController::API`
does not include layout support.

To enable layout rendering, you can include `ActionView::Layouts` manually,
then use `layout "your_own_layout"` as usual:

```ruby
module Api
  class BaseController < ActionController::API
    include ActionView::Layouts

layout "api"
  end
end
```

Without this, Rails will silently skip the layout, which can be tricky to notice.

## Change key format
By default, keys are not formatted. This is intentional. By being explicit with your keys,
it makes your views quicker and more easily diggable when working in JavaScript land.

If you must change this behavior, override it in an initializer and cache the value:

```ruby
# default behavior
Props::BaseWithExtensions.class_eval do
  # json.firstValue "first"
  # json.second_value "second"
  #
  # -> { "firstValue" => "first", "second_value" => "second" }
  def key_format(key)
    key.to_s
  end
end

# camelCased behavior
Props::BaseWithExtensions.class_eval do
  # json.firstValue "first"
  # json.second_value "second"
  #
  # -> { "firstValue" => "first", "secondValue" => "second" }
  def key_format(key)
    @key_cache ||= {}
    @key_cache[key] ||= key.to_s.camelize(:lower)
    @key_cache[key]
  end

def result!
    result = super
    @key_cache = {}
    result
  end
end

# snake_cased behavior
Props::BaseWithExtensions.class_eval do
  # json.firstValue "first"
  # json.second_value "second"
  #
  # -> { "first_value" => "first", "second_value" => "second" }
  def key_format(key)
    @key_cache ||= {}
    @key_cache[key] ||= key.to_s.underscore
    @key_cache[key]
  end

def result!
    result = super
    @key_cache = {}
    result
  end
end
```

## Escape mode

PropsTemplate runs OJ with `mode: :rails`, which escapes HTML and XML characters
such as `&` and `<`.

## Contributing

See the [CONTRIBUTING] document. Thank you, [contributors]!

[CONTRIBUTING]: CONTRIBUTING.md
  [contributors]: https://github.com/thoughtbot/props_template/graphs/contributors

## Special Thanks

Thanks to [turbostreamer], [oj], and [jbuilder] for the inspiration.

[1]: https://github.com/thoughtbot/superglue
[turbostreamer]: https://github.com/malomalo/turbostreamer
[jbuilder]: https://github.com/rails/jbuilder
[oj]: https://github.com/ohler55/oj/

props_template

Explore Similar Repositories

Was this content helpful?

Recent Feedback

Download README