It's not very likely to have more modes of search besides normal and
trashed, but got surprised in that way quite often and it's nicer this
way anyways.
A new query/request parameter can be used to apply a search to only
soft-deleted items.
The query expression `Trashed` has been introduced which selects only
items with state `Deleted`. This is another option an analog to
`ValidItemStates` (both cannot be used together as they would select
no items). This new query node is not added to the parser, because
users may not use it in their own queries - it must be part of the
"fixed" query so the application can control in which subset to search
(it would otherwise be possible to select any items).
When deleting items via the http api, they are not deleted anymore but
a new status "Deleted" is set. The collective insights contains now a
count separately for deleted items.
When an item is deleted in detail view, the results must be updated to
reflect the new state. The results are now changed by removing the
corresponding item.
Fixes: #920
The tag category is a bit special (sadly). The options are retrieved
by going through the tags. It must not update these, if a query
selects only a subset of tags.
A long attempt to simplify or shorten nested sentences without affecting the information content:
Line 179: As normal user i don't know what a "Glob" is.
Line 190: "...die hier definiert wird..." --> I think that's redundant. Where else? Or not?
Line 196: ...löschen (falls *kein* Zielordner angegeben ist). --> would actually be enough or?
I think in German one speaks more of "Absender", "Empfänger" and "Unternehmen". Is "Ausstattung" better than "Zubehör"? I think the due date implies the date in German usage. The date could therefore be left out.
Since the equipment is only available from the recipient, in my opinion the recipient could be left out. The position in the sidebar must of course always be arranged under recipient.
The time the user selects this field it should be pushed to the
server, because the initial value of "false" is a correct value. All
other fields require the user to type something first.
