Download the PHP package nystudio107/craft-twigfield without Composer

DEPRECATED

Twigfield is now deprecated; please use nystudio107/craft-code-editor instead, which is a general purpose code editor that also does Twig & autocompletes.

Twigfield for Craft CMS 3.x & 4.x

Provides a twig editor field with Twig & Craft API autocomplete

Requirements

Twigfield requires Craft CMS 3.0 or 4.0.

Installation

To install Twigfield, follow these steps:

1. Open your terminal and go to your Craft project:

   cd /path/to/project

2. Then tell Composer to require the package:

   composer require nystudio107/craft-twigfield

About Twigfield

Twigfield provides a full-featured Twig editor with syntax highlighting via the powerful Monaco Editor (the same editor that is the basis for VS Code).

Twigfield provides full autocompletion for Twig filters/functions/tags, and the full Craft CMS API, including installed plugins:

And it adds hover documentation when you hover the cursor over an expression:

You can also add your own custom Autocompletes, and customize the behavior of the editor.

Twigfield also provides a Yii2 Validator for Twig templates and object templates.

Using Twigfield

Once you've added the nystudio107/craft-twigfield package to your plugin, module, or project, no further setup is needed. This is because it operates as an auto-bootstrapping Yii2 Module.

Twigfield is not a Craft CMS plugin, rather a package to be utilized by a plugin, module, or project.

It can be very easy to add to an existing project, as you can see from the Preparse field pull request that adds it the Preparse plugin.

In the Craft CP

Twigfield works just like the Craft CMS forms macros that should be familiar to plugin and module developers.

Import Macros

Simply import the macros:

Multi-line Editor

Then to create a textarea multi-line editor, do the following:

...where textAreaText is a variable containing the initial text that should be in the editor field. This will create the Twig editor.

To create a textareaField multi-line editor, do the following:

...where textAreaText is a variable containing the initial text that should be in the editor field. This will create the label and instructions, along with the Twig editor.

Single-line Editor

Then to create a text single-line editor, do the following:

...where text is a variable containing the initial text that should be in the editor field. This will create the Twig editor that is restricted to a single line, for simple Twig expressions.

To create a textField single-line editor, do the following:

...where text is a variable containing the initial text that should be in the editor field. This will create the label and instructions, along with the Twig editor that is restricted to a single line, for simple Twig expressions.

Regardless of the macro used, an Asset Bundle containing the necessary CSS & JavaScript for the editor to function will be included, and the editor initialized.

In Frontend Templates

By default, Twigfield will not work in frontend templates, unless you specifically enable it.

Do so by copying the config.php file to the Craft CMS config/ directory, renaming the file to twigfield.php in the process, then set the allowFrontendAccess setting to true:

Then import the macros:

Create your own <textarea> element and include the necessary JavaScript, passing in the id of your textarea element:

Enabling the allowFrontendAccess setting allows access to the twigfield/autocomplete/index endpoint, and add the twigfield/templates directory to the template roots.

Additional Options

The textarea, textareaField, text, textField, and includeJs macros all take four additional optional parameters:

fieldType

fieldType - an optional 2nd parameter. By default this is set to Twigfield. You only need to change it to something else if you're using a custom Autocomplete (see below)

e.g.:

wrapperClass

wrapperClass - an optional 3rd parameter. An additional class that is added to the Twigfield editor wrapper div. By default, this is an empty string.

e.g.:

The monaco-editor-background-frame class is bundled, and will cause the field to look like a Craft CMS editor field, but you can use your own class as well.

There also a monaco-editor-inline-frame bundled style for an inline editor in a table cell (or elsewhere that no chrome is desired).

Both of these bundled styles use an accessibility focus ring when the editor is active, which mirrors the Craft CP style.

editorOptions

editorOptions - an optional 4th parameter. This is an EditorOption passed in to configure the Monaco editor. By default, this is an empty object.

e.g.:

twigfieldOptions

twigfieldOptions - an optional 5th parameter. This object that can contain any data you want to pass from your Twig template down to the Autocomplete. This can be leveraged in custom Autocompletes to pass contextual for a particular field to the Autocomplete (see below)

e.g.:

Using Additional Autocompletes

By default, Twigfield uses the CraftApiAutocomplete & TwigLanguageAutocomplete, but it also includes an optional EnvironmentVariableAutocomplete which provides autocompletion of any Craft CMS Environment Variables and Aliases.

If you want to use the EnvironmentVariableAutocomplete or a custom Autocomplete you write, you'll need to add a little PHP code to your plugin, module, or project:

The above code will add Environment Variable & Alias autocompletes to all of your Twigfield editors.

However, because you might have several instances of a Twigfield on the same page, and they each may provide separate Autocompletes, you may want to selectively add a custom Autocomplete only when the fieldType matches a specific.

Here's an example from the Sprig plugin:

This ensures that the SprigApiAutocomplete Autocomplete will only be added when the fieldType passed into the Twigfield macros is set to SprigField.

Additionally, you may have an Autocomplete that you want to pass config information down to when it is instantiated. You can accomplish that by adding the Autocomplete as an array:

Note that all of the above examples add Autocompletes to the Autocompletes that Twigfield provides by default (CraftApiAutocomplete and TwigLanguageAutocomplete). If you want to replace them entirely, just empty the types[] array first:

Writing a Custom Autocomplete

Autocompletes extend from the base Autocomplete class, and implement the AutocompleteInterface

A simple Autocomplete would look like this:

The $name property is the name of your Autocomplete, and it is used for the autocomplete cache.

The $type property is either AutocompleteTypes::TwigExpressionAutocomplete (which only autocompletes inside of a Twig expression) or AutocompleteTypes::GeneralAutocomplete (which autocompletes everywhere).

The $hasSubProperties property indicates whether your Autocomplete returns nested sub-properties such as foo.bar.baz. This hint helps Twigfield present a better autocomplete experience.

CompleteItem::create() is a factory method that creates a CompleteItem object. You can use the Fluent Model setters as shown above, or you can set properties directly on the model as well. The CompleteItem::add() method adds it to the list of generated Autocompletes.

Your Autocomplete also has a $twigfieldOptions property which will contain any data passed down via the optional 5th twigfieldOptions parameter from your Twig template. This allows you to have contextual information this a particular field.

See the following examples for custom Autocompletes that you can use as a guide when creating your own:

• TrackingVarsAutocomplete
• SprigApiAutocomplete
• CraftApiAutocomplete
• EnvironmentVariableAutocomplete
• TwigLanguageAutocomplete

Twig Template Validators

Twigfield also includes two Twig template Validators that you can use to validate Twig templates that are saved as part of a model:

• TwigTemplateValidator - validates the template via renderString()
• TwigObjectTemplateValidator - validates the template via renderObjectTemplate()

You just add them as a rule on your model, and it will propagate the model with any errors that were encountered when rendering the template:

You can also add in any variables that should be presents in the Twig environment:

For the TwigObjectTemplateValidator, you can also pass in the object that should be used when rendering the object template:

Twigfield Roadmap

Some things to do, and ideas for potential features:

• Perhaps a general code editor as an offshoot?
• Add a handler for parsing method return parameters, so we can get autocomplete on things like craft.app.getSecurity().
• Figure out why the suggestions details sub-window doesn't appear to size itself properly to fit the documentation. It's there, but you have to resize the window to see it, and it appears to be calculated incorrectly somehow
• Smarter Twig expression detection
• Hovers for TwigExpressionAutocompletes should only be added if they are inside of a Twig expression
• It would be nice if SectionShorthandFieldsAutocomplete completions presented sub-item completions, too

Brought to you by nystudio107