Standa Lukeš

Just a few comments on some details of the specification: ### Arrays Your proposal does not handle nested arrays well, we could not have an array with `"elementType": "array"`. I...

> However, I'd prefer to use the C# syntax so I suggest int[] instead of [int]. The point is, that `["int"]` can be written in JSON, so we would not...

I'm sorry, but encrypted/signed values don't work with static commands, and I don't see a reasonable way to make it work. We should however produce a more reasonable error, probably...

But then the deserialization is not possible, since the signed part of an object is missing. You could work around this by having a property with selected row **index**, instead...

We tried to fix this issue today with @acizmarik, but it was harder than expected. Let me briefly explain what are the problems: To fix this, we basically need to...

You can keep the `AggregateMarkupFileLoaderOptions` class, just replace the `Type` list with `IMarkupFileLoader` list. It's bit more annoying to use (you need to insert as a specific index), but you...

> dependencies passed in the constructor - for historical reasons, they are set to null because it was implemented before DotVVM was using IServiceProvider. I don't think so, the arguments...

@tomasherceg What can we do about this? Shall we also use the dotvvm serializer static command arguments? (this is certainly a breaking change) Or call it a "feature"?

Now, I don't know if you mean banning everything except `@service` in the instance parameter or introducing a different way to deserialize it by not deserializing it at all and...

We can not, `IQueryable` nor the `IQueryProvider` does not have any async method - https://docs.microsoft.com/cs-cz/dotnet/api/system.linq.iqueryable-1, https://docs.microsoft.com/cs-cz/dotnet/api/system.linq.iqueryable-1?view=netframework-4.7.2