Open mabvanaartrijk opened 3 months ago
@sagilio @sociometry @AsakusaRinne
@mabvanaartrijk why size 12 is the limit? Does this have anything to do with size?
@hsluoyz @mabvanaartrijk
@sagilio We now have a policy size of 14, possibly in the future we have use cases that need a few more. I understand that expanding the generic support has some drawbacks.
Would it be possible to add support for matcher functions outside the generic support? I'm now looking at creating custom eval functions that deserialize the string objects. I guess this will work too.
Hi, we ran into an issue where the eval() or other matcher functions are not supported for large request or policy sizes:
Results in an error:
DynamicExpresso.Exceptions.ParseException : No property or field 'Age' exists in type 'String' (at index 5).
It seems that when context.View.SupportGeneric is false all request arguments are handled as strings. Would it be possible to add support for this? Or do you recommend a workaround? Thanks!