fix: Gracefully handle missing column settings in pnl win
Pnl window settings are stored with the workspace on the server (like all shell window settings), and may originate from an older version of Spark with a different set of columns. We shouldn't crash if this happens.
This commit is contained in:
1 parent
dc08945719
commit
e4d8b00df2
1 file changed
+3
-1
@@ -28,7 +28,9 @@ namespace bts.shell.pnl {
|
||||
foreach (var t in _triggers) {
|
||||
foreach (var kv in t.trigger(data)) {
|
||||
if (!bd.TryGetValue(kv.Key, out var app)) {
|
||||
app = _defaults[kv.Key];
|
||||
if (!_defaults.TryGetValue(kv.Key, out app)) {
|
||||
continue;
|
||||
}
|
||||
}
|
||||
app = kv.Value.merge(app);
|
||||
bd[kv.Key] = app;
|
||||
|
||||
Reference in new issue
Block a user