github quazardous/qdadm @quazardous/qdadm@2.52.0

latest release: @quazardous/qdadm@2.53.0
one hour ago

Minor Changes

  • 85a1589: CardsDashboard gets a catalogue, cards with parameters, the size each person picks and named sections (#5348, lot 3 of #5337). A block declared card: { repeatable: true, params } is added from "Add a card" as many times as wanted, each instance with its parameters (a form drawn from the JSON Schema, checked before the card is added) merged into the block's props; a classic Zone does not show it. The catalogue also lists the hidden cards. Each card's bar has its size (s, m, l, among card.sizes) and, with sections, its section; "Add a section" groups the cards under names, edited in place. The arrangement is now v: 2 (sizes, sections, sectionOf, instances); a v1 one migrates as it is, and an instance whose block is gone or whose parameters no longer fit is dropped.

  • 6186b0a: Ready-made dashboard cards (#5339, lot 1 of #5337).

    • QdCard, the envelope every card shares: title, status (critical | watch | good | info, a side bar, a hue and a word), source and freshness, the surface link to the domain's board and the main action ({ verb, count, mode: 'next' | 'list', to | run | onClick }), the loading, unreachable, empty and invalid states, sizes s | m | l.
    • registerCard({ type, component, meta, schema }) and QdCardView: a card type ships its sheet and the JSON Schema of its data; data that does not fit draws the invalid state with its reasons instead of breaking the board.
    • The generic cards metric, queue, goal and bullet, data only, drawn in SVG and CSS.
    • QdCardsGallery: every registered card in each size, state and theme.
    • The qdadm-cards CLI and @quazardous/qdadm/cards/tools (writeCardsIndex, checkCards): the index and the bestiary (docs/cards.md) generated from the sheets, and their check.
  • 0acd437: Eight more generic cards (#5355, lot 5 of #5337), each with its sheet, schema and example, in the index, the bestiary and the gallery: compare (two values and the change, in points or percent), trend (a curve with its band of normal, the points outside marked and counted), ranking (the first N, with optional bars), split (a total, one stacked bar with a fixed palette by rank and "others", each part written), funnel (steps scaled to the first, the loss between steps in words), heat (a grid on a five-step sequential scale, each cell's value in its title), agenda (what is coming, a time today, "tomorrow", a date) and feed (what happened, the latest first, a status as a mark and a word).

  • e8982df: QdDomainBoard, a domain's board (#5352, lot 4 of #5337): the level between a dashboard and a list. The app declares typed blocks on a grid of 12 columns: kpi (a number, its note, its status as a side bar and a word), breakdown (bars scaled within each group, the value written), top (a small table with text, mono, tags, number and spark columns, each row opening its item, a "more" link) and timeline (one bar per day or hour, the latest outlined, the total and its change on the period before). Each block takes data or reads its own with load(), and draws its own loading, unreachable (with a retry), empty and invalid states, its data checked against the type's JSON Schema; the header gives the source, its freshness and a link. registerBoardBlock() adds a type of the app's own.

  • 4544111: Favourites and recents (#5349, lot 3b of #5337). A star beside the page title (QdFavoriteStar, drawn by ListPage, ShowPage and FormPage in edit mode, :favorite="false" to turn it off) adds the page to the person's favourites; "Save this search" on a filtered list keeps the list with its query under a name. The show and edit pages record the records opened lately (at most 20); a deleted record leaves both. They live in two entities the app declares, favorites ({ kind, label, to, entity, at }) and recents ({ entity, itemId, label, to, at }), read and written through their managers; configureFavorites() names others or turns one off, and without the entity the star does not show. useFavorites() and useRecent() read and change them; QdFavoritesCard and QdRecentCard show them live, through the new built-in card types favorites and recent.

  • 355de46: homeRoute: { name, component, path } gives the home page an address of its own: the page is mounted on path and / redirects to it, so a link to it survives a change of home. Without path, the page still lives on / only, and development warns about it. The breadcrumb's house icon and the 404 page's "Back to Home" now follow the home route the app declares, whatever its name (#5365).

  • 5b6d32e: A run walks a set of items one after the other from their edit or show page (#5343). QdRunBar, drawn by FormPage and ShowPage when the URL carries ?run=, says "Book 3 of 14 to process" with the filter and the order, has Previous / Next (and K / J), and a strip of done, urgent and current items. In a run, a form's Save & Close becomes "Save and go to the next"; at the end, the run says so and goes back where it started. Runs start from a filtered list on their own (opening a row walks the list's rows), from list.startRun(), from a card's action.run, or from useRun().start(). Leaving a changed form for another record of the same page now asks first, as leaving the page does.

Don't miss a new qdadm release

NewReleases is sending notifications on new releases.