Tab titles name the record; Guides reach a site and the contract surface
This commit is contained in:
18
CHANGELOG.md
18
CHANGELOG.md
@@ -90,6 +90,24 @@ ADR-007 and ADR-002.
|
||||
|
||||
### Fixed
|
||||
|
||||
- **Every detail page had the same browser tab title.** A machine, a PC and a
|
||||
printer all read "West Jefferson ShopDB - Machine" or the equivalent, so two
|
||||
tabs on two different records were indistinguishable, a bookmark said nothing
|
||||
about what it pointed at, and a link shared into Teams previewed as the
|
||||
section rather than the thing. Detail pages now name the record: machines,
|
||||
PCs, printers, network devices, subnets, measuring tools, USB devices,
|
||||
printed parts, applications, employees, knowledge base articles and guides.
|
||||
A record with no usable name, or one that failed to load, keeps the section
|
||||
name, and a long name is cut at a word boundary. Report pages gained proper
|
||||
titles too, which also fixes "Pc Relationships".
|
||||
|
||||
- **Guides would have been dropped at provisioning.** The plugin was missing
|
||||
from `deploy/site-profile-universal.json`, the profile the released Windows
|
||||
installer is built from, so the wizard would not have offered it and
|
||||
`flask plugin prune-schema` drops the tables of any plugin absent from the
|
||||
profile (ADR-014). Its model also imported core directly rather than through
|
||||
`shopdb.api`, which the contract test catches.
|
||||
|
||||
- **The shipped catalog offered two ways to spell the same vendor, and one row
|
||||
that should never have left a test.** `HP Inc.` and `Zebra Technologies` were
|
||||
empty rows duplicating `HP` and `Zebra`, which carry every model between
|
||||
|
||||
Reference in New Issue
Block a user