Codeer.LowCode.Blazor 1.3.21

• net8.0

  • Codeer.LowCode.Blazor.Licensing (>= 1.3.0)
  • Microsoft.AspNetCore.Components.WebAssembly (>= 8.0.4)
  • Microsoft.AspNetCore.Http.Abstractions (>= 2.1.1)
  • Microsoft.AspNetCore.WebUtilities (>= 8.0.4)
  • Microsoft.CodeAnalysis.CSharp (>= 4.9.2)

- Scripts: constructor arguments are now converted to the parameter types in the same way as method arguments. Since numbers in scripts are decimal, calls such as "new DateTime(year, month, day)" with computed values used to fail with "constructor not found"; overload selection follows the same rules as method calls.
- List summary rows (ListSummaryRow) can now specify horizontal alignment per cell from scripts: SetHorizontalAlignment(fieldName, HorizontalAlignment.Start/Center/End) - the same enum the layouts use; Stretch means "not specified" and falls back to the column's alignment. Merged cells (MergeColumns) follow the leading column's setting.
- Fixed new list rows created with data (AddRow/AddRows/InsertRow/InsertRows taking a Module or ModuleData) silently losing their values on submit: the passed values went through the load-time initialization path, were not treated as modifications, and the server received an Add entry carrying only the Id (all columns NULL). The row is now created empty (except the Id, so new-row detection is unchanged) and the values are applied as modifications without data interaction - IsModified is set, but OnDataChanged scripts, link-data fetches (one server round trip per row), and re-render notifications do not run, keeping bulk creation fast. Fields left null are still omitted on submit so DB column defaults keep working.
- New API for custom fields: FieldBase/Module.SetDataWithoutInteractionAsync applies field data as a modification without data interaction (no OnDataChanged, no link fetch, no notifications). The base implementation delegates to SetDataAsync so existing custom fields never lose values; fields that can apply data without interaction should override it.
- ClearError is now virtual and recurses into child modules: clearing a ListField also clears its rows' fields, a ModuleField clears its child module, and a SearchField clears its condition module. Module.ClearError (C#/pro-code) clears every field of the module recursively.
- Fixed the "unsaved changes will be lost" warning appearing on sort-header clicks and page changes even after an auto-submit (AutoSubmitField) had already saved the changes. The check now evaluates the live IsModified state at click time instead of a value captured at render time.
- Fixed a module placed in the page frame header (HeaderDesign.ModuleName) not stretching to the full header width, so its layout could not push a trailing column to the right edge. The header CSS expected the module's root grid to be a direct child of the navbar container, which stopped being true once the module root was wrapped to carry its class name.
- Fixed DeleteTogether deleting only the first page of child rows when the child list's search condition has LimitCount set. LimitCount is the display page size and is no longer applied when collecting the rows to cascade-delete; all matching child rows (including grandchildren in nested configurations) are now deleted.
- Scripts (breaking): fractional numbers passed from scripts to .NET are now truncated toward zero everywhere an integer is expected - method and constructor arguments, indexer arguments and array indexes, array sizes, and property/field/array-element assignments - matching the documented conversion rule shared by assignment, cast, and script function arguments (they used to be rounded). Code that relied on rounding should call Math.Round explicitly.