592ff49abe
core.js still routed plugin-owned pages directly. Extracted all 11 into the owning plugin's route file + moved their views into plugins/<name>/frontend/: - computers: reports/pc-relationships, settings/pctypemapping - printers: reports/toner, settings/printertypes, settings/zabbix (toner/supply monitoring) - machines: settings/machinetypes - network: settings/networktypes - warranty: settings/dellwarranty - slides: settings/slides (its route file gains a default export; it was toplevel-only) - employees: NEW plugin frontend (employees/:sso + settings/employeedirectory) - employees had no route file before; its pages lived only in core.js. core.js now holds only core routes; all 14 bundled plugins are self-contained under plugins/<name>/frontend/. Verified live: the extracted Machine Types settings page renders in the settings rail from the machines plugin frontend. Build + 58 vitest + naming green.
36 lines
898 B
JavaScript
36 lines
898 B
JavaScript
/**
|
|
* Machines plugin routes
|
|
*/
|
|
export default [
|
|
{
|
|
path: 'settings/machinetypes',
|
|
name: 'machinetypes',
|
|
component: () => import('./views/MachineTypesList.vue'),
|
|
meta: { requiresAuth: true, requiresAdmin: true, plugin: 'machines' }
|
|
},
|
|
{
|
|
path: 'machines',
|
|
name: 'machines',
|
|
component: () => import('./views/MachinesList.vue'),
|
|
meta: { plugin: 'machines' }
|
|
},
|
|
{
|
|
path: 'machines/new',
|
|
name: 'machine-new',
|
|
component: () => import('./views/MachineForm.vue'),
|
|
meta: { requiresAuth: true, plugin: 'machines' }
|
|
},
|
|
{
|
|
path: 'machines/:id',
|
|
name: 'machine-detail',
|
|
component: () => import('./views/MachineDetail.vue'),
|
|
meta: { plugin: 'machines' }
|
|
},
|
|
{
|
|
path: 'machines/:id/edit',
|
|
name: 'machine-edit',
|
|
component: () => import('./views/MachineForm.vue'),
|
|
meta: { requiresAuth: true, plugin: 'machines' }
|
|
}
|
|
]
|