Closed ascott18 closed 3 months ago
ToLower operation in string search operations:
Doesn't seem like a big enough impact to be worth changing this now.
Of all the attributes we're considering deprecating, DtoIncludes and DtoExcludes are used far and away the most in existing projects. I've changed my mind on these and will not be deprecating them at this time - their alternative of creating a whole custom Restriction feels a bit too heavy of a migration path.
Breaking (major)
(ItemResult, IncludeTree)
to just use the include tree prop on ItemResult<>.ref includetree
, makeitem
not a ref. Add an async variant.Breaking (minor)
ToLower
operation in string search operations (if this is harming DB performance. TODO: compare query plans between sql with the lowering operation and SQL without it to see if there's a plan difference when the searched column is indexed and the search operation can use the index (StartsWith and Equals).$withSimultaneousRequestCaching
to$useSimultaneousRequestCaching
. Also consider adding a version that is specific to an ApiCaller instance, for parity with features like $useResponseCaching.Deprecations
DtoIncludesAttribute
andDtoExcludesAttribute
SelectFilter
TypeScriptPartial
[ControllerAttribute]
. Added for IPC. Unused by every other project.[CreateControllerAttribute]
. WillCreateView=false is knockout only. WillCreateApi=false is redundant with adding Deny permission to Read, Create, Edit, Delete. Globally disabling kinds of generated code for all types (e.g. disable all views or all API controllers) can be done via code gen config (coalesce.json).[LoadFromDataSourceAttribute]
. Niche attribute, very rarely used. Merge into ExecuteAttribute?