commit ea671be69b121a5336082113a0fb040315345c6a
author Matthias Villiger <mvi@bsi-software.com> Mon Nov 26 11:37:20 2018 +0100
committer Matthias Villiger <mvi@bsi-software.com> Mon Nov 26 14:11:48 2018 +0100
tree 9e0376d696ced8a7e86dddb310c597b7574fe319
parent 13eac1e1ee4e85fe4ebeb90d37dd422e2f676618

Decrease log level for TableData which cannot be mapped to a UI column

A table extension can be limited to a table that exists in a specific
scope. This works for the UI where e.g. the new column is then only
added if the correct scope (form) is available.
The registration of the TableData extension on the other hand is always
done for all scopes of that DTO because DTOs never know their scope (in
which FormData is the TableData currently used?). Therefore it is not
possible to register a DTO extension with scope because the extension
could then never be found because in a DTO the scope is never known.
This asymmetry leads to the situation that the contribution is available
in the table DTO even if the column is not available in the UI (because
in the UI the scope is evaluated and the extension is not added).
In that situation a warning was logged that the UI column could not be
found for the (mostly) empty extension data. Because this actually
works as designed and cannot be changed, a warning is not necessary.
Therefore the log level was decreased to debug.

237273