feature/ui-fixes

[iruzevic]

Description

Version 10.3.0 — a set of UI/compatibility fixes.

Changed

• Updated the $schema path in all block and component manifests to point to eightshift-frontend-libs-tailwind instead of eightshift-frontend-libs, so manifest schema validation resolves correctly.

Fixed

• Fixed arbitrary values not working in the col-end-span-* Tailwind utility (grid-column-end: span --value([*]) was missing), which caused incorrect field widths.
• Fixed a broken field style attribute on older projects — field, checkboxes and radios now normalize a non-array fieldStyle value into an array before it reaches FormsHelper::getTwFieldStyleOutput(), preventing a breakage on projects that still store it as a string.

QA Guide

Steps for QA to test this feature:

1. Open a form in the block editor and set a field width using an arbitrary column value (e.g. a custom width on a field inside a grid).
2. Check the rendered form on the frontend — the field should respect the width set in the editor.
3. Open a form on an older project (one migrated from a pre-Tailwind version) that has a field style saved as a single string value, and render it on the frontend.
4. Confirm the field, checkboxes and radios components render without a PHP error or notice.
5. Open any manifest.json in src/Blocks/components or src/Blocks/custom in an editor with JSON schema support and confirm the schema resolves without errors.

Expected result: Field widths render as configured, older projects with string field styles render without errors, and manifest schemas validate against eightshift-frontend-libs-tailwind.

Screenshots / Videos

Linked documentation PR