[checkmk-commits] [tribe29/checkmk] f1b9c2: Fix: handle Visual create_info with no context

Branch: refs/heads/master Home: https://github.com/tribe29/checkmk Commit: f1b9c295093f246c00eb30eb9d4ecb3f3bad7e72 https://github.com/tribe29/checkmk/commit/f1b9c295093f246c00eb30eb9d4ecb3f3… Author: Hannes Rantzsch <hannes.rantzsch(a)tribe29.com> Date: 2023-01-05 (Thu, 05 Jan 2023) Changed paths: M cmk/gui/dashboard/visual_type.py M cmk/gui/plugins/visuals/utils.py M cmk/gui/views/visual_type.py M cmk/gui/visuals/__init__.py Log Message: ----------- Fix: handle Visual create_info with no context JS may provide no context, so the Pydantic model has to deal with that. Adjust visual handler types as far as possible; often it is not clear if context will be required. Change-Id: I1bcf41e1fc3c9b4f69357dda1797cdfb8f454fcc Commit: 5ca30b5a7797674b38d7399bea0bb47edd4839d1 https://github.com/tribe29/checkmk/commit/5ca30b5a7797674b38d7399bea0bb47ed… Author: Hannes Rantzsch <hannes.rantzsch(a)tribe29.com> Date: 2023-01-05 (Thu, 05 Jan 2023) Changed paths: M cmk/gui/visuals/__init__.py Log Message: ----------- Fix serialization of LazyStrings in Visuals Builtin visuals contain LazyStrings. Copying a builtin visual to the users' visuals resulted in serializing the LazyString via repr to l"some string", which cannot be deserialized using literal_eval. This led to unavailability of the reports page for all users if a user attempted to modify the default template with their visuals. LazyStrings are now explictly evaluated to fixed str's when saving Visuals. CMK-11706 Change-Id: I3ccb11cd006be260c10c2eac4fc6f2dfc3aa78b4 Compare: https://github.com/tribe29/checkmk/compare/996ed09db5d7...5ca30b5a7797