Replies: 1 comment
-
AFAIR it was done intentional.
This was done to support users who either grab or discover many trackables in a row.
This was implemented based on a feature request to make it possible to handle some TBs in inventory different to others. The two use cases have a different entry point (dedicated TB log vs. cache log), therefore I think it could stay as it is. |
Beta Was this translation helpful? Give feedback.
-
During refactoring of logging (for log edit/delete) I noticed that we have two different behaviours implemented wrt Trackable action prefill.
("Action" in context of Trackable means the log type e.g. NOTE, VISITED, RETRIEVED, DROPPED and so on)
Question: is this behaviour intentional? If not, how should it be changed?
Things to consider:
One idea would be to combine both. Use following logic in BOTH places:
Beta Was this translation helpful? Give feedback.
All reactions