Paul Schneider
b3056f1c2e
Lives in Yavsc.Blogs (not Yavsc.Api) because Yavsc.Api is not yet enabled in production; future migration to Yavsc.Api is a single namespace + route prefix change. Endpoint: GET /api/user-search?q=<name>&e=<email>&take=<n> - Authorisation: [Authorize] (any authenticated caller). - q: case-insensitive substring match on FullName OR UserName. - e: case-insensitive exact match on Email. - take: 1..100, default 25. Returns a flat UserSearchResultDto (Id, UserName, FullName, Avatar, Email) — no navigation properties, so the payload stays small even if the user table grows. The Email field is included because the address-book use case (composing circle membership, sending invites) needs it. On Yavsc's single-tenant deployments the user table is a closed community; multi-tenant deployments should gate this controller behind a tenant-scoped policy before exposing it. The trade-off is documented in the controller's class-level XML doc. |
||
|---|---|---|
| .. | ||
| cli | ||
| PostIt | ||
| PostIt.Tests | ||
| Yavsc.Abstract | ||
| Yavsc.Api | ||
| Yavsc.Api.Client | ||
| Yavsc.Blogs | ||
| Yavsc.Blogs.Tests | ||
| Yavsc.Org | ||
| Yavsc.Org.Tests | ||
| Yavsc.Server | ||
| Yavsc.Tests.Shared | ||