All notable changes to @escalated-dev/escalated will be documented in this file.
-
pages.jsonnow publishes the props each page reads, alongside the names it already published, and which of those the component declares required.The names let a backend catch a page that renders into nothing. The props are the same fault one level down, and the one nothing could see: a backend that sends
datato a component readingperiod_daysrenders the chrome and no content, on a 200 — and an empty report reads as a quiet week rather than a wiring fault. Twenty-seven report screens across four backends are in exactly that state today.Read out of the compiler's own binding metadata rather than matched out of the source, so a
definePropsspread over lines, given types, or written as an array still reports what Vue will actually accept.
-
The workflow builder sent a shape no backend reads. It posted
trigger: 'ticket_created', conditions as{match, conditions}and actions as{type, config}. Every backend engine evaluatestrigger_eventwith dotted names (ticket.created), conditions as{all: [...]}or{any: [...]}, and actions as{type, value}. So a workflow built here failed validation on Laravel, and wherever it did save it could never match an event.The builder now sends the body fixed in escalated-developer-context
domain-model/workflow-admin-contract.md. It still opens workflows stored in the older shapes, including Laravel's{match, rules}, and saves them back in the new one. -
The builder offers what the backend can actually do.
Formhands thetrigger_events,action_typesandoperatorsa backend sends to the builder, in any of the three shapes the contract allows, instead of swallowing them. Without them it offers the contract's defaults: five triggers, the core action catalog and twelve operators. Operators no backend evaluates (in,matches) and fields no backend resolves (type,assigned_agent,reply_count,custom_field) are gone. -
The workflows list showed every workflow as disabled. It read
active, and backends sendis_active. Toggling now POSTs to the toggle route, which is a POST everywhere, where it used to PUT. Reordering sendsworkflow_ids.
-
Error.vue, the refusal and not-found screen.escalated-railsrendersEscalated/Errorfor every 403 and 404 inside the panel and no component has ever existed behind it, so a refusal arrived as a blank page — and a refusal that says nothing is indistinguishable from a bug.It takes the
statusand the backend's already-translatedmessage, and falls back to its own wording when a status arrives bare. Like the two-factor challenge it does not useEscalatedLayout: the usual reason to be here is having been refused, and the layout's navigation is a list of places the viewer may equally not be allowed to go. The way back is rendered only when the backend says where that is, since a host mounts Escalated under its own prefix and this page is reached without a layout to resolve one.
-
Auth/TwoFactorChallenge.vue, the post-login two-factor challenge.escalated-adonishas been renderingEscalated/Auth/TwoFactorChallengewith no component behind it, so the challenge screen was blank — and a blank challenge is not a locked door, it is a dead end for anyone with 2FA enabled.It deliberately does not use
EscalatedLayout: the sign-in is not finished at that point, and nothing on the page should suggest access that has not been granted. A TOTP code and a recovery code post to the same endpoint, and only the field in use is sent, so a blank companion field cannot read as an attempt with an empty code.
-
pages.jsonwas not in the published package.fileslisted onlysrc, so the manifest every backend is meant to check its own page names against was exported, documented, and absent from the tarball.exportsandfilesare independent lists and nothing compares them, sonpm publishsaid nothing.tests/packaging.test.jsnow reads the real file list fromnpm pack --dry-run --jsonand fails if any path named inexportsis not in it.
-
resolveEscalatedPage(), so a page name with no component behind it says so. Inertia resolves an unknown name to nothing: Vue renders nothing and the panel comes up blank on a 200 response, which reads as a permissions problem or an empty dataset. It is how four screens shipped blank. The resolver throws in development, naming what was asked for and the nearest thing that exists, and in production logs the same message rather than rendering an empty page.createInertiaApp({ resolve: (name) => resolveEscalatedPage(name, () => resolvePageComponent(`./Pages/${name}.vue`, import.meta.glob('./Pages/**')), ), });
Suggestions are ranked on path-segment overlap rather than leaf equality — nearly every page ends in
IndexorForm, so matching on the last segment ranks half the package equally. -
pages.json, the list of every page name this package can resolve, generated fromsrc/pagesand exported at@escalated-dev/escalated/pages.json. It is what each backend checks its own page names against in CI, which is the only place both halves of that comparison are known.npm run pages:checkfails if it has drifted from the components, and CI runs it.
-
The package could not be published at all.
@escalated-dev/localewas depended on as a git reference —github:escalated-dev/escalated-locale#v0.1.8— and npm refuses to fetch git-type packages while publishing:npm error code EALLOWGIT npm error Fetching packages of type "git" have been disablednpm publishfailed for v0.10.0 and v0.11.0, leaving 0.9.0 as the latest version on the registry while two releases sat tagged and unpublished. The same package is on npm as@escalated-dev/locale@0.1.8; it is now depended on from there.A git dependency is also invisible to Dependabot, so nothing was ever going to flag it.
-
Automations screens (
Admin/Automations/Index.vue,Admin/Automations/Form.vue). Six backends renderEscalated/Admin/Automations/*and this package had no component behind either name, so the screen came up blank — Inertia resolves a missing page to nothing rather than to an error. Automations are the time-based half of the admin automation surface; Workflows are the event-driven half. They are separate surfaces and both need a screen.The form offers only the fields, operators and actions the backend runner actually evaluates. Anything else would save cleanly and then silently never match a ticket.
-
Public tickets settings (
Admin/Settings/PublicTickets.vue). Rendered by five backends, previously blank. Each guest policy mode asks for exactly the value the backend requires alongside it, because a mode saved without its companion value is rejected server-side and the field has to be on screen to be filled in. -
Plugin pages (
Plugin/Page.vue). A plugin declares a route on the backend and a component on the frontend, and this is where the two meet. Two backends renderEscalated/Plugin/Page; with nothing behind the name, every plugin page was blank — and blank in the same way whether the plugin was installed on the frontend or not. It now resolves the registered component, and names what is missing when there is none. -
Admin/Workflows/Form.vue, the name the backends render for the workflow editor.Builder.vueis the editor and takes exactly these props; the name simply had no page behind it. -
scripts/audit-page-parity.py, which compares every page name the backends render against the components this package ships. That comparison is the only way to see this class of bug: the request succeeds, the tests pass, and the screen is empty. -
An
Automationsentry in the admin navigation. The screen the backends render had no way in.
- Test runner on vitest 5, with
@storybook/*10.6 and happy-dom 20.14. The suite runs in roughly half the time. .gitattributesnormalising line endings. Prettier'sendOfLinedefaults tolf, so a Windows checkout withcore.autocrlf=truefailedformat:checkon files that were perfectly formatted — a failure that appeared only on a contributor's machine and never in CI.
- Database connection settings screen (
Admin/Settings/DatabaseConnection.vue). Shows which database Escalated is reading and writing, lists the connections it could use, probes each without committing to it, and switches between them. An unmigrated or unreachable connection is disabled with the reason shown — pointing Escalated at a database with no Escalated tables does not error, it renders an empty panel, which reads exactly like data loss. Whenescalated.connectionis pinned in config the form is not rendered at all.
- Newsletter system admin UI (Wave 0). Full Vue/Inertia admin surface for the newsletter feature: compose / index / show pages, deliveries table, analytics tiles, dynamic segment-filter builder, list-member table, markdown editor, merge-field dropdown, preview iframe, and supporting components + Storybook stories. (#75)
usePermissions()composable and permission-gated admin navigation — the newsletter nav entry renders only for users holdingnewsletters.manage, matching the backend permission enforcement (escalated-laravel #129). (#96)- Consume translations from
@escalated-dev/localeas the canonical base source, withsrc/locales/*.jsonretained as local plugin overrides that win over central. PublicuseI18n().t()/$tAPI is unchanged.
- Newsletter admin pages wired to locale strings (i18n). (#96)
peerDependencies."@inertiajs/vue3"widened from^1.0.0 || ^2.0.0to^1.0.0 || ^2.0.0 || ^3.0.0. Host apps on@inertiajs/vue33.x no longer trip annpm installpeer-dep conflict. We use onlyLink,router,useForm, andusePagefrom this package, all stable across the v1/v2/v3 line.
- Widget's API endpoint path is now configurable via
data-widget-path(on the script tag) /widgetPathoption (oncreateEscalated). Default stays/support/widgetfor backward compatibility. Unblocks NestJS hosts where the base path isn't/support. useChat()threads the resolvedwidgetPaththrough all six chat API endpoints; AgentTicketShow,ActiveChatsPanel,ChatQueuereadpage.props.escalated?.prefixto build the right path on the agent side.
- Ticket type/category support — ticket type and category in list view, filters, sidebar, and create form
- Configurable table columns and view tabs for the ticket queue
- Advanced search with expanded ticket search capabilities
- Panel theming support via
EscalatedPlugin, with panel theme tokens migrated across all layouts, CRUD pages, shared components, reports, settings, and ticket pages - Light/dark mode with full light-mode agent panel story, ARIA accessibility across all components, and panel theme preview in Storybook
- Import wizard — Vue pages, exports, i18n strings, and Zendesk import adapter plugin with admin nav link
- Knowledge base pages — frontend pages, components, and Knowledge Panel in ticket sidebar
- Automations admin pages (triggers, rules, categories)
- Webhooks admin pages
- Capacity admin page with AgentLoadIndicator component
- Skills admin pages with SkillTagManager component
- Side conversations — SideConversation and SideConversationList components
- Ticket merging — TicketMergeDialog component
- Ticket linking — TicketLinkPanel and TicketTypeSelector components
- Custom Fields admin pages
- Custom Statuses admin pages
- Business Hours admin pages
- Audit Log frontend
- Agent Roles frontend
- Reporting — dashboard, chart/KPI components, agent productivity metrics, SLA achievement reporting with compliance chart, CSAT settings and report pages
- Context panel framework for ticket view
- Sandbox environment placeholder page
- Custom objects frontend pages
- Conditional fields rule builder and visibility logic
- Advanced email channel settings page
- Data retention settings page
- Two-factor authentication frontend components
- SSO (SAML/JWT) settings page
- Collision warning component and typing indicator for agent collaboration
- Light agent restrictions in TicketShow
- "Powered by Escalated" badge with admin toggle
- Storybook and GitHub Actions screenshot workflow with Playwright tests and auto-generated README images
- Plugin hooks expansion for richer extension use cases
- Consolidated plugins page, keyboard shortcuts, and presence indicator polish
- Migrated all components to panel theme tokens (replacing direct dark-mode branches)
- Updated navigation, exports, and tests for platform parity
- Extracted shared constants, formatting utils, and debounced search into reusable modules
- Screenshots run only on tagged releases in CI
- README updated with WordPress, Filament, React Native, Flutter frameworks and Plugin Development section
- Ticket search reliability improvements
- StatsCard tests updated for panel theme tokens
- Export count test updated for new shared utils, composables, and admin import pages
- Husky pre-commit hook cross-platform compatibility (Windows and Mac/Linux)
- Hero screenshots now transparent with rounded corners
Initial public release.