Shopify / Shopify/liquid

Is there a way to list all of the "variables" available?

Open
#1,254 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Ruby
Stars
11.9k
Forks
1.5k
Avg merge
17h 55m
Merged PRs (30d)
3

Description

Is there a way to list all of the variables available?
Variables may be the wrong word but it should be clarified below.

I am a customer of Zendesk and they use Liquid for some of their formatting.
But, they are not the greatest at keeping up with the documentation of the new variables they have created. They call them placeholders.
https://support.zendesk.com/hc/en-us/articles/203662156-Zendesk-Support-placeholders-reference

Use Case: As a user, I would like the ability to use Liquid to output all of the available variables. In my case something like {{listvariables}} would output the following:
user.organization.name
user.organization.is_shared
user.organization.is_shared_comments
user.organization.details
user.organization.notes
user.organization.tags

ticket.comments
ticket.public_comments
ticket.latest_comment
ticket.latest_public_comment placeholders.
ticket.public_comments
ticket.latest_comment
ticket.latest_public_comment

comment.author.name
comment.created_at
comment.created_at_with_time
comment.is_public
comment.value
comment.value_rich
comment.id
comment.attachments
attachment.filename
attachment.url

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no implementation files, entry points, or tests. Start by reviewing Liquid's variable-resolution behavior and the linked Zendesk placeholder reference, then seek maintainer guidance on scope; completion would require an agreed way to enumerate available variables and corresponding tests or documentation.

Written by the indexing model from the issue text.

Assessment

Tech stack
ruby
Domain
web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.