Merge branch 'main' into copilot/fix-578-2

Author: ascott18

CHANGELOG.md

@@ -22,13 +22,15 @@
 - `ListViewModel.$orderByToggle()` method added to cycle through ascending, descending, and no ordering for a field.
 - Custom methods now support descriptions via `DescriptionAttribute`. These are displayed in the admin pages. 
 - Added `FileTypeAttribute` to control allowed file types for custom method file parameters.
+- Added `ClientCacheDurationSeconds` property to `ExecuteAttribute` to customize client-side cache duration for GET custom methods with `VaryByProperty`.
 - `c-admin-display`: Binary values now render as links that will download the value as a file, instead of only showing the length in bytes.
 - `c-datetime-picker`: Added prop `showTodayButton`
 - `c-input`: Added a `filter` prop for enum inputs to restrict the values available for selection.
 - `c-select`: When bound to a `ViewModel` or `ViewModelCollection`, selected items are converted to `ViewModel` instances before being emitted so that event handlers will receive the final object instance, rather than the intermediate plain model instance.
 - `c-select`: Now supports binding to a non-many-to-many collection navigation property. Selecting an item will populate the foreign key of the dependent item, and deselecting an item will clear the foreign key. This mechanism is only available when using c-select directly - it is not delegated by c-input.
 - `c-select`: The `create` prop now supports a `position` property to control whether the create item appears at the start ('start', default) or end ('end') of the dropdown list.
 - `c-select-many-to-many`: The `itemTitle` prop now receives the existing selected middle entity instance, if there is one.
+- `c-loader-status`: Added `show-success` prop and flag to display success messages when operations complete successfully.
 
 ## Fixes
 - Fix error in codegen when using JS reserved keywords or C# contextual keywords as parameter names.

docs/cspell.json

@@ -3,13 +3,15 @@
     "language": "en",
     "words": [
         "appsettings",
+        "ASPNETCORE",
         "autosave",
         "autosaving",
         "Axios",
         "bootstrap-datetimepicker",
         "Coalesce",
         "coalesceko",
         "coalescevue",
+        "discoverability",
         "dontSerialize",
         "dtos",
         "EF",
@@ -18,11 +20,12 @@
         "instanceof",
         "IntelliTect",
         "mkdir",
+        "msword",
         "nameof",
-        "overridable",
-        "discoverability",
         "netcoreapp",
         "netstandard",
+        "officedocument",
+        "openxmlformats",
         "overridable",
         "POCOs",
         "queryable",
@@ -31,6 +34,8 @@
         "readonly",
         "snapshotted",
         "Stampable",
+        "swashbuckle",
+        "Swashbuckle",
         "TPCT",
         "treeshaken",
         "typeof",
@@ -41,9 +46,9 @@
         "Vitest",
         "Vuetify",
         "webp",
-        "wwwroot",
-        "Swashbuckle",
-        "swashbuckle"
+        "westus",
+        "wordprocessingml",
+        "wwwroot"
     ],
     "ignorePaths": [
         "node_modules"

docs/package.json

@@ -18,6 +18,7 @@
     "gray-matter": "^4.0.3",
     "linkcheck-bin": "file:linkcheck-bin-3.0.0-1.fix-issue-56.tgz",
     "serve-handler": "^6.1.6",
-    "vitepress": "2.0.0-alpha.5"
+    "vitepress": "2.0.0-alpha.5",
+    "wait-on": "^8.0.4"
   }
 }

docs/stacks/vue/coalesce-vue-vuetify/components/c-loader-status.md

@@ -46,6 +46,13 @@ Wrap a save/submit button:
 </c-loader-status>
 ```
 
+Show success alerts when operations complete successfully:
+``` vue-html
+<c-loader-status :loaders="person.$save" show-success>
+    <button> Save </button>
+</c-loader-status>
+```
+
 Hides the table before the first load has completed, or if loading the list encountered an error. Don't show the progress bar after we've already loaded the list for the first time (useful for loads that occur without user interaction, e.g. `setInterval`):
 
 ``` vue-html
@@ -119,13 +126,14 @@ no-error-content?: boolean;
 no-initial-content?: boolean;
 no-progress?: boolean;
 no-initial-progress?: boolean;
-no-secondary-progress?: boolean;" lang="ts" id="flags-props" />
+no-secondary-progress?: boolean;
+show-success?: boolean;" lang="ts" id="flags-props" />
 
 Component level [flags](#flags) options that control behavior when the simple form of `loaders` (single instance or array) is used, as well as provide baseline defaults that can be overridden by the advanced form of `loaders` (object map) .
 
 ## Flags
 
-The available flags are as follows, all of which default to `true`. In the object literal syntax for `loaders`, the `no-` prefix may be omitted to set the flag to `true`.
+The available flags are as follows, all of which default to `true` except for `show-success` which defaults to `false`. In the object literal syntax for `loaders`, the `no-` prefix may be omitted to set the flag to `true`.
 
 | <div style="width:160px">Flag</div> | Description |
 | - | - |
@@ -135,6 +143,7 @@ The available flags are as follows, all of which default to `true`. In the objec
 | `no-progress` | Master toggle for whether the progress indicator is shown in any scenario. |
 | `no-initial-progress` | Controls whether the progress indicator is shown when an API Caller is loading for the very first time (i.e. when  `caller.wasSuccessful === null`). |
 | `no-secondary-progress` | Controls whether the progress indicator is shown when an API Caller is loading any time after its first invocation (i.e. when  `caller.wasSuccessful !== null`). |
+| `show-success` | Controls whether success alerts are shown when API calls complete successfully (i.e. when `caller.wasSuccessful === true`). |
 
 ## Slots
 

docs/stacks/vue/getting-started.md

@@ -75,7 +75,7 @@ If any of the options you chose above require external integrations, you'll need
 
 ### AppHost Project
 
-The AppHost project is a [.NET Aspire](https://learn.microsoft.com/en-us/dotnet/aspire/get-started/aspire-overview) dev-time orchestration project. It is recommended you set this as your startup project when developing, although this is not strictly required if your project only has SQL Server as its sole dependency. If you're not familiar with .NET Aspire, you're strongly encouraged to read through its [overview documentation](https://learn.microsoft.com/en-us/dotnet/aspire/get-started/aspire-overview#dev-time-orchestration) and learn about the features of the [Aspire dashboard](https://learn.microsoft.com/en-us/dotnet/aspire/fundamentals/dashboard/explore).
+The AppHost project is a [.NET Aspire](https://learn.microsoft.com/en-us/dotnet/aspire/get-started/aspire-overview) dev-time orchestration project. It is recommended you set this as your startup project when developing, although this is not strictly required if your project only has SQL Server as its sole dependency. If you're not familiar with .NET Aspire, you're strongly encouraged to read through its [overview documentation](https://learn.microsoft.com/en-us/dotnet/aspire/get-started/aspire-overview) and learn about the features of the [Aspire dashboard](https://learn.microsoft.com/en-us/dotnet/aspire/fundamentals/dashboard/explore).
 
 ### Data Project
 

docs/topics/audit-logging.md

@@ -117,9 +117,9 @@ public class AppDbContext : DbContext, IAuditLogDbContext<AuditLog>
 
 ### Exclusions & Formatting
 
-Coalesce's audit logging is built on top of [Entity Framework Plus](https://entityframework-plus.net/ef-core-audit) and can be configured using all of its [configuration](https://entityframework-plus.net/ef-core-audit#scenarios), including [includes/excludes](https://entityframework-plus.net/ef-core-audit-exclude-include-entity) and [custom property formatting](https://entityframework-plus.net/ef-core-audit-format-value).
+Coalesce's audit logging uses Entity Framework's change tracking capabilities to automatically detect and record changes to your entities. It intercepts the `SaveChanges` operation to capture entity state changes and property modifications before they're committed to the database.
 
-Coalesce will not use EF Plus's `AuditManager.DefaultConfiguration` global singleton instance. You must use Coalesce's configuration extensions which allow for more targeted configuration per context that does not rely on a global static singleton. For example:
+You can configure which entities and properties to include or exclude from auditing, as well as customize how property values are formatted in the audit logs. Coalesce's configuration extensions allow for targeted configuration per context without relying on global static singletons. For example:
 
 ``` c#
 public class AppDbContext : DbContext, IAuditLogDbContext<AuditLog>

docs/topics/security.md

@@ -686,7 +686,7 @@ For a more complete explanation of everything you can do with behaviors, see the
 
 Since Coalesce's data access layer is built on top of Entity Framework, you can also use [Entity Framework's Global Query Filters](https://learn.microsoft.com/en-us/ef/core/querying/filters) feature to apply row-level security.
 
-This approach is less flexible than custom Coalesce data sources and has other [drawbacks](https://learn.microsoft.com/en-us/ef/core/querying/filters#accessing-entity-with-query-filter-using-required-navigation) as well, but on the other hand it has more absolute authority, is less susceptible to issues like inadvertently returning data through unfiltered navigation properties, and can sometimes require less work to implement than individual data sources.
+This approach is less flexible than custom Coalesce data sources and has other [drawbacks](https://learn.microsoft.com/en-us/ef/core/querying/filters#query-filters-and-required-navigations) as well, but on the other hand it has more absolute authority, is less susceptible to issues like inadvertently returning data through unfiltered navigation properties, and can sometimes require less work to implement than individual data sources.
 
 Global Query Filters are also the only way to implement database-executed [filtered includes](#filtered-includes) of [reference navigation properties](https://learn.microsoft.com/en-us/ef/core/modeling/relationships/glossary), as there is no version of `.Include()` for reference navigation properties that allows a database-executed predicate to be applied. See [this open issue](https://github.com/dotnet/efcore/issues/24422) on EF Core.
 

docs/topics/working-with-dates.md

@@ -186,7 +186,7 @@ services.AddCoalesce(builder => builder
 
 ### Client-Side Configuration
 
-You can configure a default timezone for your client application to control how `DateTimeOffset` values are displayed in the UI. By default, this uses the client computer's timezone and does not need to be configured unless you want to override this. See [Time Zones](/modeling/model-types/models.md#time-zones) for more details.
+You can configure a default timezone for your client application to control how `DateTimeOffset` values are displayed in the UI. By default, this uses the client computer's timezone and does not need to be configured unless you want to override this. See [Time Zones](/stacks/vue/layers/models.md#time-zones) for more details.
 
 You can override this on a per-component or per-operation basis using the `timeZone` format option described above.