Resource Views

A resource view is one of the screens Fleetbase uses to list and show records: the table of drivers, orders or invoices, and the details view that opens when you click one. Every engine that ships with Fleetbase (Fleet-Ops, Storefront, Ledger, IAM and Developers) builds its screens this way.

Each of those views has a set of registries: named places where an extension can add its own items. Your extension registers an item once, from its extension.js, and the view renders it next to its own, with no change to the engine that owns the view.

What You Can Add

To a Table View

To a Details View

How It Works

Three pieces fit together:

1. A registry name says where the item goes. It reads like a path: the engine, the resource, the kind of view, and the slot.

   fleet-ops : driver : table : columns
   ───┬─────   ──┬───   ──┬──   ───┬───
   extension  resource  surface   slot

   See Registry Names.

2. A contract says what the item is. Each kind of item has its own class from @fleetbase/ember-core/contracts:

   Contract	Used for
   TableColumn	Columns
   ResourceAction	Row actions, bulk actions and details menu items
   ActionButton	Toolbar buttons and details header buttons
   MenuItem	Details tabs

3. The resource-view service stores your item under that name. The view reads the registry when it renders and merges your items in with its own.

// addon/extension.js
import { TableColumn } from '@fleetbase/ember-core/contracts';

export default {
    setupExtension(app, universe) {
        const views = universe.getService('resource-view');

        views.register(
            'fleet-ops:driver:table:columns',
            new TableColumn({ id: 'acme-safety-score', label: 'Safety Score', valuePath: 'meta.safety_score' })
        );
    },
};

That is a complete registration: the drivers table now has a Safety Score column. Getting Started builds it up step by step, with a custom cell and a placement.

Where to Go Next

Requirements

Resource view registries need @fleetbase/ember-core 0.3.25 and @fleetbase/ember-ui 0.4.5 or later in the console, and these engine versions or later:

On an older console, registering does nothing and the views render as they always have, so your extension keeps working.