\Aksara\Laboratory\Core->setAttribute()

The documentation and cheat sheet of our framework

setAttribute() adds raw HTML attributes to generated fields.

Purpose

setAttribute() adds raw HTML attributes to generated fields. It lets a controller customize Aksara Core behavior while keeping the request inside the built-in CRUD, rendering, permission, validation, and response pipeline.

When to Use

Use it when the generated table, form, or read view is mostly correct but one or more fields need custom behavior.

Reference

setAttribute(string|array $params = [], ?string $value = null)

Parameters

Parameter	Type	Required	Default	Description
`$params`	`string\|array`	No	`[]`	String value or associative array of values, depending on the method.
`$value`	`?string`	No	`null`	Value assigned to the given key or field.

Return Value

static

Returns the current controller instance so it can be chained with other Core methods.

Behavior

setAttribute() updates field metadata used by the renderer. The generated output changes when the table, read, or form view is rendered.

[!WARNING]
Attributes are rendered into generated controls. Do not pass untrusted raw request data directly into this method.

Basic Usage

$this->setAttribute('slug', 'data-source="title" autocomplete="off"');

return $this->render('orders');

Advanced Usage

$this->setAlias(['created_at' => phrase('Created'), 'updated_at' => phrase('Updated')])
    ->setValidation(['title' => 'required|max_length[160]', 'status' => 'required'])
    ->fieldOrder('title, slug, status, created_at');

Complete Example

namespace Modules\Orders\Controllers;

use Aksara\Laboratory\Core;

class Orders extends Core
{
    public function index()
    {
        $this->setTitle(phrase('Orders'))
            ->setAttribute('slug', 'data-source="title" autocomplete="off"');

        return $this->render('orders');
    }
}

Result

The generated table, form, or read view uses the configured field behavior when the response is prepared.

Notes

This method is chainable and returns the current controller instance.
Field names must match table columns, selected aliases, relation aliases, or mock fields.
Most field configuration methods accept a single field/value pair or an associative array for bulk configuration.