pastilhas
05d51302ec
The owner installed it, landed on the configuration form, and could not get off it. Not a bug in the form: there was nothing behind it. One panel was registered and it was the settings. That is the wrong shape for a plugin regardless of how much is finished. A screen whose only content is its own configuration reads as broken rather than unfinished, because the first thing anybody does after installing is look for the way forward. So: collections on the left, links on the right, and the settings behind the gear in the collections panel - reachable when something is wrong and out of the way when it is not. Selection is `?collection=` in the URL rather than a channel, so which collection you are looking at survives a reload and can be linked to. Search is Linkwarden's own `searchQueryString`, which searches names, descriptions, tags AND the archived page text - the thing a bookmark bar cannot do, and the reason this is worth more than a list of addresses. Doing it here would mean pulling every link to the browser and would still only see the fields we happened to fetch. Verified against the instance: 50 unfiltered, 8 for "arch", 0 for a string matching nothing. The panel holds no credential and could not send one. Every request goes through the authenticated door, which finds the caller's mapped account and puts their token on. `no Linkwarden account is mapped to you` is the state every user starts in, so it is said as an instruction rather than rendered as an outage.
19 lines
1.1 KiB
TypeScript
19 lines
1.1 KiB
TypeScript
import type { AppRegistryMeta } from 'officerdev';
|
|
import { Bookmark, FolderTree } from 'lucide-react';
|
|
import { CollectionsPanel } from './CollectionsPanel';
|
|
import { LinksPanel } from './LinksPanel';
|
|
|
|
// Two panels: what you have saved, and how it is filed.
|
|
//
|
|
// It was one — the settings form — and that was the mistake worth naming. A plugin whose only screen is
|
|
// its configuration is one you cannot leave: nothing is behind it, so the first thing anybody does after
|
|
// installing is look for the way forward and not find one. The settings are a disclosure inside the
|
|
// collections panel now, reachable when something is wrong and out of the way when it is not.
|
|
//
|
|
// `availableOnPanel: false` keeps them out of the generic picker: they belong to the /linkwarden screen
|
|
// rather than being things to drop into an arbitrary dashboard.
|
|
export const appRegistryMetas: AppRegistryMeta[] = [
|
|
{ key: 'linkwarden-collections', name: 'Collections', icon: FolderTree, component: CollectionsPanel, availableOnPanel: false },
|
|
{ key: 'linkwarden-links', name: 'Links', icon: Bookmark, component: LinksPanel, availableOnPanel: false },
|
|
];
|