История коммитов

simba77
feat(collections): show the sections of a collection as one tree
The sections tab shows the whole tree at once, each section under its parent in the order of the collection, drawn like the tree of the forum, instead of one level at a time opened with Open. A section counts the items of its subtree, as the link to its items does, with its own when they differ; its menu edits it, lists its items, adds an item or a subsection in it and deletes it in a dialog. Saving or deleting a section returns to the tree.

The paged query of one level of sections is gone; the tree is built from every section of the collection with its item count.
simba77
feat(collections): rebuild the list of the items of a collection
The items tab is a live list: a search by the name, the code or the id, the section with everything under it (or the items outside every section) and the status — published, hidden, scheduled or expired. A row shows where the item stands, whether the site shows it, when it changed, and the values of the fields the collection marks for the list; its menu edits it, opens it on the site and deletes it in a dialog that returns to the same page of the list.

A field gets "Show in the list of items" (migration: collection_fields.in_list). The panel has a query of its own for the list, separate from the query API of the site; the sections of a collection are read as a tree (SectionTree). Numbers are shown in full: a price is not shortened to 75K.
simba77
feat(collections): give every collection a page with tabs
A collection is one page in the panel now: its name, a link to it on the site, and a tab for its items, sections (when it uses them), fields and settings, each with what it holds. The parts of a collection were separate pages reached only through the list.

The list of the collections is a table with the number of items, sections and fields and whether a collection is public, API only or turned off; a row opens the collection, its menu leads to every part of it. The settings moved from /admin/collections/{id}/edit to the settings tab (the old address is gone), laid out in cards with the deleting of the collection at the bottom. A new collection opens on its fields. Deleting a collection, field, section or item asks in a dialog; the collection's says what goes with it.

The public address of a collection is worked out by the model, and the list and the head take it from there.
simba77
feat(news): draw the sections of the panel like the tree of the forum
The tree of the sections is worked out by GetNewsListUseCase::getSectionTree(): what the filter lets through, the sections above a found one, the depth below the section the list is narrowed to, and the articles of every subtree. The row mapper only draws it.

The top sections get the tinted row and bold name of the tree of the forum, the sections a search only passes through are dimmed, and a narrowed list starts at the left edge. The number of articles counts the subtree, as the link it leads to does, with the section's own when they differ. The date of creation is gone; the date of the last change stays. Tests cover the order, the depth, the search and the counts.
simba77
refactor(news): drop the flat list of sections
The sections of the panel are listed as a tree from every section at once, so the paged and ordered list they came from is gone: the section query and count of the repository, the use case method that read them, and the column of the number of articles in the order of the list. Only the articles are ordered by a column now.
simba77
fix(consent): name the accounts and format the dates of the consent log
The log shows the name of an account that still exists, linked to its profile, and only the id of one deleted since, without a link to a profile that is gone. Dates are formatted like the rest of the panel. The title of a consent no longer has its id glued to it: the fallback for a deleted consent took the whole expression because ?? binds tighter than ~.

The actions of the consent list are aligned to the right edge, and Total: is translated.
simba77
feat(admin): offer Save and close in the menu of Save
A form that returns to its list gets Save with a menu instead of a third button, so the footer stays on one line on a phone and in the languages with long words. The menu is positioned absolutely: the backdrop filter of a sticky footer would make the footer the frame of a fixed menu and move it away from its button.
simba77
feat(admin): keep the buttons of long forms in view
The account, news settings, contacts, forum section and news section forms run past two screens on a phone; their footers are sticky now, like those of the ad, role and article forms.
simba77
fix(admin): finish every form with the shared footer
The forms of an account, its roles, antiflood, karma, the forum and news settings and the consents had rows of buttons of their own: a filled Cancel, Save first or on the left. They use form-footer now, which needs no form id when it stands inside the form. The contacts and cookie banner settings get Cancel back to the panel like the other settings pages. The roles of an account had lost the alignment of their buttons with the style removed in the previous commit.
simba77
fix(admin): keep one set of buttons in a form
The buttons of a form are only under it now: the head keeps its links (messages, open on the site) but no longer repeats Save. The role, forum section, news article and news section forms had a row of their own under the form; it is the shared form-footer now, which offers Save and close for the forms that return to a list. form-buttons is folded into form-footer.