Codeer.LowCode.Blazor 1.3.0

• 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)

This release adds device/screen-size landing for page frames, proportional column scaling, list replace modes, and real-time cascading select fields, and unifies the type-conversion rules of the scripting engine. It includes breaking changes that may affect existing scripts.

[ New Features ]

- Page Frames: Application-root page frames can now be selected by device and screen size. Each page frame has a TargetDevice (Any / PC / Touch) and a WidthFrom (minimum screen width). On root-URL access (for example after login), the page frame that matches the current device and screen width is opened; among the matches the largest WidthFrom that fits wins, and ties are broken by Priority. Existing apps are unaffected (defaults are Any and no width).
- Grid Layout: Added IsProportionalScale on grid rows. When enabled, each column's Width is treated as a ratio rather than a fixed pixel size, so the columns grow and shrink proportionally as the row width changes. (Every column in the row must have a Width; MinWidth / MaxWidth, column resize, wrapping, and flow layout cannot be combined with this mode.)
- List Field: Added a ReplaceMode (data replacement). "All" deletes all rows matching the search condition and re-inserts the current rows; "UpdateAsDeleteInsert" turns updates into delete-then-insert so that swapping unique-key values between rows no longer hits constraint violations. The default ("None") keeps the previous add/update/delete behavior.
- Number Field: Added an OnInput event that fires in real time on every keystroke (and continuously while dragging a slider), before the value is committed and OnDataChanged fires. The script function receives the in-progress value as an argument ("void Func(decimal? value)"; null while the input cannot be parsed as a number). The field's Value itself is still updated only when the input is committed, as before.
- Select Field: Cascading (dependent) select fields now refresh their candidates in real time when the field they depend on changes, and a selected value that is no longer a valid candidate is cleared automatically.
- Select Field: A loaded value that is not among the current candidates is now added to the candidate list (shown with its stored display text) and kept selected, so opening existing data no longer blanks the display or silently changes the stored value. The value also survives candidate reloads (cascading refresh, SetCandidates) as long as it is unchanged; once the user selects a different value, out-of-candidate values are cleared as before. If the display text collides with an existing candidate, the value is shown in parentheses after the text (with a numbered suffix if still ambiguous).

[ Breaking Changes ]

- Scripting: Converting a fractional number to an integer type now truncates toward zero instead of rounding (matching C# cast semantics). This applies consistently to assignments, initializers, casts, function arguments, and return values. For example, (int)1.9 and "int x = 1.9;" now yield 1 (previously 2).
- Scripting: Converting a non-null value that cannot be converted into a non-nullable type now raises a runtime error. In particular, reassigning an unconvertible value to a typed variable previously became null silently; it now raises an error. (Assigning null to a non-nullable value type still produces its default value, for example "int x = null;" yields 0 and "DateTime x = null;" yields DateTime.MinValue; conversion into a nullable type still results in null.)
- Scripting: Casting a string to a numeric type now performs the conversion instead of returning the string unchanged. For example, (int)"5" now yields 5.
- Scripting: (int)null now yields 0 instead of null, consistent with "int x = null;".
- Scripting: Fixed numeric widening in method overload resolution. Previously the widening check used an incorrect type order, so passing byte / sbyte / short / ushort / uint arguments could select an unintended overload. It now follows C# implicit numeric conversion rules, which may change which overload is chosen for such calls (cast the argument explicitly to pin the overload).

[ Bug Fixes ]

- Scripting: == and != comparisons between decimal and double / float no longer raise an error (for example, comparing a number field with a literal such as 1.5).
- Scripting: A fractional-format string assigned or cast to an integer type is now converted by truncation instead of raising an error (for example, "int x = "1.9";" yields 1).
- Search: A NotIn condition with an empty value list now matches all rows instead of none, consistent with in-memory matching. This affects both C# data-access queries and designer-defined search conditions.
- Sidebar/Menu: Links pointing to a page frame that the current user cannot access are now hidden, consistent with the existing behavior for links to inaccessible modules. Previously such page-frame links stayed visible and only showed an access-denied message when clicked.
- ExecuteSql: Fixed a defect where the DataReader was not disposed for the Reader method type, which could leave the connection busy and block subsequent commands on the same connection/transaction.
- ExecuteSql: Input and write-back now use the data member mapped to the DB column instead of always using Value, so fields whose stored value is not Value (for example a File field's file name) are read and written correctly.
- Search Layout: Fixed handling when a search layout references a missing or invalid layout name.
- Search Layout: Fixed an exception that occurred when a Link field was set to read-only in a search layout.

[ Other ]

- Scripting: Added sbyte as a supported type keyword.
- Data access (C#): Added a Take extension to the typed SearchCondition for limiting the number of rows fetched.
- Page Frames: Added a Priority setting. When a user can access more than one application-root page frame, the one with the highest Priority opens first; equal values keep the defined order. Existing apps are unaffected (the default of 0 preserves the previous order-based behavior).
- Data access (C#): SearchDelete now blocks dangerous empty executions. Deleting with no search condition raises an error, and deleting every row must be requested explicitly, to prevent accidentally wiping out an entire table.
- Fields: A field whose IsEnabled is false now shows the standard disabled (gray) background, in both list cells and detail layouts, so it is visually distinct from a read-only (transparent) field. This applies to all UI field types (text, number, select, boolean, radio, date/time, link, button, file). In a list cell the gray fills the whole cell; in a detail layout it covers the control area.
     To restore the previous appearance (disabled = no background), add the following to your project's app.css (it can also be placed in a PageFrames/{name}.css side-car file to revert only that page frame):

       #app td input.form-control:disabled,
       #app td textarea.form-control:disabled,
       #app td select.form-select:disabled,
       #app td .cl-disabled-bg,
       #app td .link-field-container.disabled,
       #app td button.btn-outline-secondary:disabled {
         background: transparent !important;
       }

       #app td .cl-disabled-bg-fill::before {
         background: transparent !important;
       }