Releases: escalated-dev/escalated
Releases · escalated-dev/escalated
Release list
v0.9.0 — Newsletter system admin UI
Newsletter system admin UI (Wave 0)
The shared Vue/Inertia frontend now ships the full newsletter admin surface, consumed identically by every Escalated backend.
Added
- Newsletter admin UI — compose / index / show pages, deliveries table, analytics tiles, dynamic segment-filter builder, list-member table, markdown editor, merge-field dropdown, preview iframe (+ Storybook stories). (#75)
usePermissions()composable + permission-gated admin nav — the newsletter entry renders only for users withnewsletters.manage, matching backend enforcement. (#96)- Central translations consumed from
@escalated-dev/locale; localsrc/locales/*.jsonwin as overrides.
Changed
- Newsletter admin pages wired to locale strings (i18n). (#96)
Full Changelog: v0.8.0...v0.9.0
v0.8.0 - Admin users page + staff-panel banner on /support
Added
- Admin → Users page (#62): a paged, searchable list of host users at
/support/admin/userswith toggles to grant or revokeis_admin/is_agent. Lands aUsersentry in the admin nav between Roles and Capacity. Self-demote on the Admin toggle is disabled in the UI and rejected server-side. Pairs withescalated-laravel#94. Surfaced from #60, where the reporter asked "how do you create agent?" - Staff-panel banner on
/support(#61): the customer index scopes its ticket list to the current user, so admins / agents who landed on/supportsaw only their own tickets and concluded that customer-submitted tickets were invisible to staff. Customer tickets are visible in/support/admin/ticketsand/support/agent/tickets— the new banner just makes that path obvious from the customer view.
Backwards compatibility
Both additions are forward-compatible. The Users page assumes hosts are using the is_admin / is_agent columns the install command suggests; hosts wiring the gates differently (Spatie roles, etc.) can override the controller in the companion Laravel package.
Full Changelog: v0.7.1...v0.8.0
v0.7.1 — Inertia v3 + configurable widget path
Changed
peerDependencies.\"@inertiajs/vue3\"widened from^1.0.0 || ^2.0.0to^1.0.0 || ^2.0.0 || ^3.0.0. Host apps on@inertiajs/vue3@3.xno longer trip annpm installpeer-dep conflict (#39). We import onlyLink,router,useForm, andusePage, all stable across the v1 → v2 → v3 line.
Fixed
- 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(#35). useChat()threads the resolvedwidgetPaththrough all six chat API endpoints; AgentTicketShow,ActiveChatsPanel,ChatQueuereadpage.props.escalated?.prefixto build the right path on the agent side.
Full Changelog: v0.7.0...v0.7.1