tsai/abp - abp - Gitea: Git with a cup of tea

Author	SHA1	Message	Date
maliming	270533e30f	Map a numeric bound only when its meaning is the same on both sides A native integer is a number in the api type system too, and a between rule that carries its own comparer is skipped when its bounds no longer read as an interval, because the comparer itself is not on the descriptor.	2 weeks ago
maliming	8e53ef8641	Map a comparison rule only to a numeric property The contribution context carries the property now, so a rule on another type, the ordinal comparison of two strings for example, no longer publishes a numeric bound. Two bounds are compared as decimals, which are exact for every integral type, and only fall back to double for the magnitudes decimal can not hold.	2 weeks ago
maliming	f92909480d	Keep a range limit that is already written in the invariant culture A magnitude below the decimal range, like 1e-30, parses to a zero, so a round trip through decimal turned it into a bound the server does not accept.	2 weeks ago
maliming	0ed8624e7a	Write the typed range limits with the invariant culture Range(Type, string, string) keeps its limits as strings until the first validation, so a numeric limit was reported in the culture that declared it and could not be merged with a FluentValidation bound.	2 weeks ago
maliming	3b011f7703	Add the Volo.Abp.Http.FluentValidation package It reflects the statically evaluable FluentValidation rules of a DTO into the api definition, so the client proxy generators see the same constraints the attributes already provide. A rule is only published when it applies to every instance of the type, which leaves out the conditional rules, the rules of a non-default rule set and the rules of a RuleForEach. Volo.Abp.FluentValidation keeps its own dependencies, it does not depend on Volo.Abp.Http.	2 weeks ago