Pascal Linxweiler
96d2f10346
Until now the UI could only reach glossaries recorded in domains.json. A
glossary can also sit on the DeepL account with no domain pointing at it —
created before this app, left over from testing, or because domains.json was
reset, which is the normal state of a fresh deployment volume. Such a
glossary is invisible and unreachable here while still consuming the
account's glossary allowance, so on a small plan one forgotten glossary
blocks every save with no way to clear it from the UI.
Adds three endpoints backed by a new section in the domain settings modal:
GET /api/glossaries what is really on the account, each
annotated with the domain using it
DELETE /api/glossaries/:id remove one, freeing a slot, and drop
any local reference to it
POST /api/glossaries/:id/adopt claim an existing glossary for a
domain, fetching its entries so they
become editable
Adopting is a move, not a copy: if another domain already referenced the
glossary, that slot is released. Two domains pointing at one glossary would
mean editing through either silently replaces what the other still lists.
This does not raise the plan's glossary limit; it makes the limit visible
and the single slot reusable without hand-editing domains.json.
Co-Authored-By: Claude <noreply@anthropic.com>
30 KiB
30 KiB