Open tengulak opened 1 week ago
Thanks for reporting the issue. I believe this one is caused by a partially fixed bug that we don't use the DotVVM serialized for input arguments and instead call the Newtonsoft.Json converter. Since the fix has the potential to break some existing code, it has to be enabled as an "experimental feature":
config.ExperimentalFeatures.UseDotvvmSerializationForStaticCommandArguments()
Newtonsoft.Json.JsonSerializationExceptionCannot deserialize the current JSON array (e.g. [1,2,3]) into type 'System.Collections.Generic.Dictionary`2[System.Int32,System.Int32]' because the type requires a JSON object (e.g. {"name":"value"}) to deserialize correctly. To fix this error either change the JSON to a JSON object (e.g. {"name":"value"}) or change the deserialized type to an array or a type that implements a collection interface (e.g. ICollection, IList) like List that can be deserialized from a JSON array. JsonArrayAttribute can also be added to the type to force it to deserialize from a JSON array.
Path 'args[0].SelectedItems', line 1, position 17440.
async Task DotVVM.Framework.Hosting.StaticCommandExecutor.Execute(StaticCommandInvocationPlan plan, Queue arguments, Queue argumentValidationPaths, IDotvvmRequestContext context)
async Task DotVVM.Framework.Utils.TaskUtils.ToObjectTask(object taskOrSomething)
Source File: _\src\Framework\Framework\Utils\TaskUtils.cs:20
async Task DotVVM.Framework.Hosting.DotvvmPresenter.ExecuteCommand(ActionInfo action, IDotvvmRequestContext context, IEnumerable methodFilters)
Source File: _\src\Framework\Framework\Hosting\DotvvmPresenter.cs:411
System.ExceptionUnhandled exception occurred in the command!