V10.0.12

.github/workflows/build-and-deploy.yml

@@ -7,7 +7,7 @@ on:
     branches:
       - master 
 env:
-  VERSION: 10.0.11
+  VERSION: 10.0.12
 jobs:
   build-and-deploy:
     runs-on: ubuntu-latest

Api.ApiClients.Audit/.claude/skills/nano-add-entity/SKILL.md

@@ -286,22 +286,22 @@ public class <Entity>QueryCriteria : BaseQueryCriteria
     {
         var expressions = base.GetExpressions();
 
-        var expression = expressions.FirstOrDefault() ?? new CriteriaExpression();
+        var expression = expressions.First();
 
         if (!string.IsNullOrEmpty(this.Name))
         {
             expression
                 .StartsWith(nameof(<Entity>.NameNormalized), this.Name.ToUpper());
         }
 
-        expressions
-            .Add(expression);
-
         return expressions;
     }
 }
 ```
 
+- `base.GetExpressions()` already returns a list holding one `CriteriaExpression`, so add the conditions to
+  that first expression and return the list as it is. Never `Add` that same expression again, it would be
+  combined with itself. Only `Add` a new `CriteriaExpression` for a separate group that is AND-ed in.
 - Only add filter properties for fields that make sense to search/filter by — don't
   mechanically add one filter per scalar property on the entity.
 - Every filter property must be `virtual` and nullable.

Api.ApiClients.Audit/.github/prompts/nano-add-entity.prompt.md

@@ -286,22 +286,22 @@ public class <Entity>QueryCriteria : BaseQueryCriteria
     {
         var expressions = base.GetExpressions();
 
-        var expression = expressions.FirstOrDefault() ?? new CriteriaExpression();
+        var expression = expressions.First();
 
         if (!string.IsNullOrEmpty(this.Name))
         {
             expression
                 .StartsWith(nameof(<Entity>.NameNormalized), this.Name.ToUpper());
         }
 
-        expressions
-            .Add(expression);
-
         return expressions;
     }
 }
 ```
 
+- `base.GetExpressions()` already returns a list holding one `CriteriaExpression`, so add the conditions to
+  that first expression and return the list as it is. Never `Add` that same expression again, it would be
+  combined with itself. Only `Add` a new `CriteriaExpression` for a separate group that is AND-ed in.
 - Only add filter properties for fields that make sense to search/filter by — don't
   mechanically add one filter per scalar property on the entity.
 - Every filter property must be `virtual` and nullable.

Api.ApiClients.Audit/AGENTS.md

@@ -258,7 +258,7 @@ public class MyUserController(ILogger<MyUserController> logger, MyApi myApi, MyO
 | Attribute   | Purpose                                                                                                       |
 | ------------- | ------------------------------------------------------------------------------------------------------------------ |
 | `[Route(Order = n)]`  | Positional route-template substitution (`{n}` placeholders in the action's route string, filled in `Order` sequence). |
-| `[Query]`             | Querystring parameter (scalar types); optional `Name` override.                                                       |
+| `[Query]`             | Querystring parameter: a scalar, a list of scalars, or an object (sent as `Name.Property=value`, such as `Paging.Number=2`); optional `Name` override. |
 | `[Body]`              | The JSON request body (one complex object).                                                                           |
 | `[Form]`              | A `multipart/form-data` field — scalar, or `IFormFile`/`FileInfo`/`FileStream`/`Stream`/`NamedStream`; complex objects need `[FromFormBody]` server-side. Mutually exclusive with `[Body]`. |
 | `[Header(Name=..., ValuePrefix=...)]` | An HTTP header key/value.                                                                              |
@@ -297,6 +297,8 @@ public class SetMyFileRequest : BaseRequest
 3. Add a method to the client, calling `InvokeAsync<TRequest>` (no response) or `InvokeAsync<TRequest, TResponse>`
    (typed response — use `NamedStream` or `Stream` for file downloads).
 
+**Paging a custom request**: give it one `[Query] public virtual Pagination? Paging { get; set; }` and have the client method set `Paging = paging`. It is sent as `Paging.Number`, `Paging.Count` and `Paging.Skip`, and the action binds it with `[FromQuery] Pagination? paging`, so `Skip` is kept. Never copy `Number` and `Count` into two scalar properties, that drops `Skip`.
+
 **Controller resolution**: if a request doesn't set `this.Controller` explicitly in its constructor, it's
 inferred as the pluralized `TResponse` type name (e.g. `IEnumerable<MyEntity>` → `MyEntities`). Set it explicitly
 whenever the route doesn't naturally match the response type, or the request has no typed response at all.
@@ -2072,19 +2074,22 @@ public class MyEntityQueryCriteria : BaseQueryCriteria
     public override IList<CriteriaExpression> GetExpressions()
     {
         var expressions = base.GetExpressions();
-        var expression = expressions.FirstOrDefault() ?? new CriteriaExpression();
+        var expression = expressions.First();
 
         if (!string.IsNullOrEmpty(this.Name))
         {
             expression.StartsWith(nameof(MyEntity.Name), this.Name);
         }
 
-        expressions.Add(expression);
         return expressions;
     }
 }
 ```
 
+`base.GetExpressions()` already returns a list holding one `CriteriaExpression`, so the conditions go on that first
+expression and the list is returned as it is. Never `Add` that same expression again: the list is AND-ed, so it would
+be combined with itself. Only `Add` a new `CriteriaExpression` for a separate group (see [Combining criteria](#combining-criteria--sequential-not-grouped)).
+
 Built on the [DynamicExpression](https://github.com/vivet/DynamicExpression) library — criteria properties are
 compiled into LINQ expressions against the entity, not hand-written `Where` clauses.
 
@@ -2212,6 +2217,14 @@ filter by a property on a **collection navigation**, wrap the nested property in
 expression.GreaterThan("Orders[Total]", 100m);   // x.Orders.Any(o => o.Total > 100)
 ```
 
+A negated operation (`NotEqual`, `NotIn`, `NotContains`) on a collection path means **no element matches**, it compiles to
+`!x.Orders.Any(...)` with the positive operation inside. Use it to leave out rows that have a related row, such as the
+users who are not in an organization:
+
+```csharp
+expression.NotEqual("OrganizationScopes[OrganizationId]", organizationId);   // !x.OrganizationScopes.Any(s => s.OrganizationId == organizationId)
+```
+
 ##### Ordering and pagination
 
 `Ordering` (`IQuery.Order`) — `By` (default `"Id"`, supports the same dotted-path navigation as criteria

Api.ApiClients.Audit/Api.ApiClients.Audit.Service.Models/Criterias/ExampleQueryCriteria.cs

@@ -18,17 +18,14 @@ public override IList<CriteriaExpression> GetExpressions()
     {
         var expressions = base.GetExpressions();
 
-        var expression = expressions.FirstOrDefault() ?? new CriteriaExpression();
+        var expression = expressions.First();
 
         if (!string.IsNullOrEmpty(this.Name))
         {
             expression
                 .StartsWith(nameof(Example.Name), this.Name);
         }
 
-        expressions
-            .Add(expression);
-
         return expressions;
     }
 }

Api.ApiClients.Entity/.claude/skills/nano-add-entity/SKILL.md

@@ -286,22 +286,22 @@ public class <Entity>QueryCriteria : BaseQueryCriteria
     {
         var expressions = base.GetExpressions();
 
-        var expression = expressions.FirstOrDefault() ?? new CriteriaExpression();
+        var expression = expressions.First();
 
         if (!string.IsNullOrEmpty(this.Name))
         {
             expression
                 .StartsWith(nameof(<Entity>.NameNormalized), this.Name.ToUpper());
         }
 
-        expressions
-            .Add(expression);
-
         return expressions;
     }
 }
 ```
 
+- `base.GetExpressions()` already returns a list holding one `CriteriaExpression`, so add the conditions to
+  that first expression and return the list as it is. Never `Add` that same expression again, it would be
+  combined with itself. Only `Add` a new `CriteriaExpression` for a separate group that is AND-ed in.
 - Only add filter properties for fields that make sense to search/filter by — don't
   mechanically add one filter per scalar property on the entity.
 - Every filter property must be `virtual` and nullable.

Api.ApiClients.Entity/.github/prompts/nano-add-entity.prompt.md

@@ -286,22 +286,22 @@ public class <Entity>QueryCriteria : BaseQueryCriteria
     {
         var expressions = base.GetExpressions();
 
-        var expression = expressions.FirstOrDefault() ?? new CriteriaExpression();
+        var expression = expressions.First();
 
         if (!string.IsNullOrEmpty(this.Name))
         {
             expression
                 .StartsWith(nameof(<Entity>.NameNormalized), this.Name.ToUpper());
         }
 
-        expressions
-            .Add(expression);
-
         return expressions;
     }
 }
 ```
 
+- `base.GetExpressions()` already returns a list holding one `CriteriaExpression`, so add the conditions to
+  that first expression and return the list as it is. Never `Add` that same expression again, it would be
+  combined with itself. Only `Add` a new `CriteriaExpression` for a separate group that is AND-ed in.
 - Only add filter properties for fields that make sense to search/filter by — don't
   mechanically add one filter per scalar property on the entity.
 - Every filter property must be `virtual` and nullable.

Api.ApiClients.Entity/AGENTS.md

@@ -258,7 +258,7 @@ public class MyUserController(ILogger<MyUserController> logger, MyApi myApi, MyO
 | Attribute   | Purpose                                                                                                       |
 | ------------- | ------------------------------------------------------------------------------------------------------------------ |
 | `[Route(Order = n)]`  | Positional route-template substitution (`{n}` placeholders in the action's route string, filled in `Order` sequence). |
-| `[Query]`             | Querystring parameter (scalar types); optional `Name` override.                                                       |
+| `[Query]`             | Querystring parameter: a scalar, a list of scalars, or an object (sent as `Name.Property=value`, such as `Paging.Number=2`); optional `Name` override. |
 | `[Body]`              | The JSON request body (one complex object).                                                                           |
 | `[Form]`              | A `multipart/form-data` field — scalar, or `IFormFile`/`FileInfo`/`FileStream`/`Stream`/`NamedStream`; complex objects need `[FromFormBody]` server-side. Mutually exclusive with `[Body]`. |
 | `[Header(Name=..., ValuePrefix=...)]` | An HTTP header key/value.                                                                              |
@@ -297,6 +297,8 @@ public class SetMyFileRequest : BaseRequest
 3. Add a method to the client, calling `InvokeAsync<TRequest>` (no response) or `InvokeAsync<TRequest, TResponse>`
    (typed response — use `NamedStream` or `Stream` for file downloads).
 
+**Paging a custom request**: give it one `[Query] public virtual Pagination? Paging { get; set; }` and have the client method set `Paging = paging`. It is sent as `Paging.Number`, `Paging.Count` and `Paging.Skip`, and the action binds it with `[FromQuery] Pagination? paging`, so `Skip` is kept. Never copy `Number` and `Count` into two scalar properties, that drops `Skip`.
+
 **Controller resolution**: if a request doesn't set `this.Controller` explicitly in its constructor, it's
 inferred as the pluralized `TResponse` type name (e.g. `IEnumerable<MyEntity>` → `MyEntities`). Set it explicitly
 whenever the route doesn't naturally match the response type, or the request has no typed response at all.
@@ -2072,19 +2074,22 @@ public class MyEntityQueryCriteria : BaseQueryCriteria
     public override IList<CriteriaExpression> GetExpressions()
     {
         var expressions = base.GetExpressions();
-        var expression = expressions.FirstOrDefault() ?? new CriteriaExpression();
+        var expression = expressions.First();
 
         if (!string.IsNullOrEmpty(this.Name))
         {
             expression.StartsWith(nameof(MyEntity.Name), this.Name);
         }
 
-        expressions.Add(expression);
         return expressions;
     }
 }
 ```
 
+`base.GetExpressions()` already returns a list holding one `CriteriaExpression`, so the conditions go on that first
+expression and the list is returned as it is. Never `Add` that same expression again: the list is AND-ed, so it would
+be combined with itself. Only `Add` a new `CriteriaExpression` for a separate group (see [Combining criteria](#combining-criteria--sequential-not-grouped)).
+
 Built on the [DynamicExpression](https://github.com/vivet/DynamicExpression) library — criteria properties are
 compiled into LINQ expressions against the entity, not hand-written `Where` clauses.
 
@@ -2212,6 +2217,14 @@ filter by a property on a **collection navigation**, wrap the nested property in
 expression.GreaterThan("Orders[Total]", 100m);   // x.Orders.Any(o => o.Total > 100)
 ```
 
+A negated operation (`NotEqual`, `NotIn`, `NotContains`) on a collection path means **no element matches**, it compiles to
+`!x.Orders.Any(...)` with the positive operation inside. Use it to leave out rows that have a related row, such as the
+users who are not in an organization:
+
+```csharp
+expression.NotEqual("OrganizationScopes[OrganizationId]", organizationId);   // !x.OrganizationScopes.Any(s => s.OrganizationId == organizationId)
+```
+
 ##### Ordering and pagination
 
 `Ordering` (`IQuery.Order`) — `By` (default `"Id"`, supports the same dotted-path navigation as criteria

Api.ApiClients.Entity/Api.ApiClients.Entity.Service.Models/Criterias/ExampleQueryCriteria.cs

@@ -18,17 +18,14 @@ public override IList<CriteriaExpression> GetExpressions()
     {
         var expressions = base.GetExpressions();
 
-        var expression = expressions.FirstOrDefault() ?? new CriteriaExpression();
+        var expression = expressions.First();
 
         if (!string.IsNullOrEmpty(this.Name))
         {
             expression
                 .StartsWith(nameof(Example.Name), this.Name);
         }
 
-        expressions
-            .Add(expression);
-
         return expressions;
     }
 }

Api.ApiClients.RootLogIn/.claude/skills/nano-add-entity/SKILL.md

@@ -286,22 +286,22 @@ public class <Entity>QueryCriteria : BaseQueryCriteria
     {
         var expressions = base.GetExpressions();
 
-        var expression = expressions.FirstOrDefault() ?? new CriteriaExpression();
+        var expression = expressions.First();
 
         if (!string.IsNullOrEmpty(this.Name))
         {
             expression
                 .StartsWith(nameof(<Entity>.NameNormalized), this.Name.ToUpper());
         }
 
-        expressions
-            .Add(expression);
-
         return expressions;
     }
 }
 ```
 
+- `base.GetExpressions()` already returns a list holding one `CriteriaExpression`, so add the conditions to
+  that first expression and return the list as it is. Never `Add` that same expression again, it would be
+  combined with itself. Only `Add` a new `CriteriaExpression` for a separate group that is AND-ed in.
 - Only add filter properties for fields that make sense to search/filter by — don't
   mechanically add one filter per scalar property on the entity.
 - Every filter property must be `virtual` and nullable.

Api.ApiClients.RootLogIn/.github/prompts/nano-add-entity.prompt.md

@@ -286,22 +286,22 @@ public class <Entity>QueryCriteria : BaseQueryCriteria
     {
         var expressions = base.GetExpressions();
 
-        var expression = expressions.FirstOrDefault() ?? new CriteriaExpression();
+        var expression = expressions.First();
 
         if (!string.IsNullOrEmpty(this.Name))
         {
             expression
                 .StartsWith(nameof(<Entity>.NameNormalized), this.Name.ToUpper());
         }
 
-        expressions
-            .Add(expression);
-
         return expressions;
     }
 }
 ```
 
+- `base.GetExpressions()` already returns a list holding one `CriteriaExpression`, so add the conditions to
+  that first expression and return the list as it is. Never `Add` that same expression again, it would be
+  combined with itself. Only `Add` a new `CriteriaExpression` for a separate group that is AND-ed in.
 - Only add filter properties for fields that make sense to search/filter by — don't
   mechanically add one filter per scalar property on the entity.
 - Every filter property must be `virtual` and nullable.