- Validation: the three enum synonyms that the renderers have always accepted - `Middle` (= `Center`) and `End` (= `Right` for `align`, `Bottom` for `alignVertical` / `cellVerticalAlign`) for alignment, and `NormalWeight` (= `Normal`) for `fontWeight` - are valid again in styles and in the node property `align` (table column); 1.2.0 rejected them as `NRP015` although they rendered correctly before. They are declared in the new `enumAliases` section of `template-schema.json` (`PropertySchema.EnumAliases` / `StylePropertySchema.EnumAliases`, additive), are not offered by the template editor, and any other unknown value is still `NRP015`. - Template editor: editing the template text on the JSON tab no longer closes the SignalR circuit for templates over about 16 KB (the Blazor Server limit for one incoming message was 32 KB, so the editor reset itself to the default template and lost the Undo history); the limit is now 4 MB (`EditorLimits.MaxHubMessageSize`, twice the 2 MB upload limit). - Validation: the format of colors in styles is now checked (new code `NRP029`, `DiagnosticCodes.InvalidColor`): `color`, `background`, `decorationColor`, `border*.color` and `shadow.color` must be a hex color `#RGB`, `#ARGB`, `#RRGGBB` or `#AARRGGBB` (the hash is optional, as with QuestPDF `Color.FromHex`) or a name from `meta.palette`, and the values in `meta.palette` are checked as well (`$.meta.palette.<name>`); an empty color is still ignored. Before, a style such as `"color": "red"` passed validation and the PDF render failed with an exception from QuestPDF. An error in strict mode, a warning in compat mode like the other style content checks; the HTML/JSON formats were more tolerant (CSS color names) but such a template could not be rendered to PDF either. The color of a `Line` node (`Line.color`) is checked the same way (reported on the node property, e.g. `$.content.root.items[1].color`; QuestPDF reads it as strictly as the colors of styles); chart colors (`series[].color`, `palette`) are checked separately and only as a warning in both modes, because OxyPlot reads only hex with a hash (`#RGB`, `#RRGGBB`, `#AARRGGBB`; also `R,G,B`), does not know color names or hex without the hash and silently falls back to `SteelBlue` (a `meta.palette` name is resolved to its value first). - A style border with an empty `color` (`"border": { "color": "" }`) now gets the default color `#000000` like a missing one; the empty string used to reach QuestPDF `BorderColor` and fail the render. - `PipelineError` (the argument of `IReportPipelineObserver.OnError`) has the new init properties `BindingDiagnostics` and `OmittedBindingDiagnostics` (additive, empty by default): when a render fails (page limit, cancellation, an exception from the renderer) the binding diagnostics collected up to the failure are delivered too, which helps to find the cause; an error in the parse stage carries an empty list. - Tables: new variables in the summary rows: `groupCount` (number of data rows of the group) in `rows.group.summary` and `totalCount` (number of all data rows) in `totalSummary`, e.g. `{{totalCount}}` or `{{# totalCount * 2 }}`; they replace the removed implicit row count of the `qty` cell. - Binding diagnostics: an invalid C# expression (compile error, reported as an error with the Roslyn code, e.g. `CS1525`) and a C# expression that throws at run time (warning with the exception type) are now reported with the JSON path instead of silently giving an empty text; the same problem on the same path is reported once per render. `IBindingEvaluator` has the new default interface method `Render(TextTemplate, DataContext, List<BindingDiagnostic>?, string?)` (custom evaluators keep compiling and report nothing); `TextTemplate.ParseDiagnostics` is new and `TextTemplateCache.GetOrParse` reports the parse diagnostics of a broken text on every path where it is used (before, only on the first one, because the text is parsed once per render), once per path. - C# expressions: methods without arguments over JSON arrays now work: `{{# root.items.Count() }}` (before, `Count()` failed silently and rendered an empty text although the property `root.items.Count` worked) and `Any()`, `First()`, `FirstOrDefault()`, `Last()`, `LastOrDefault()`; unsupported calls are reported as a warning. - Charts: a series value that cannot be converted to a number is reported once per series with the number of such values and the first one as an example (before, every different value was a separate diagnostic and flooded the limit of binding diagnostics); the value expression of a series and the `source` expressions of `repeat`, charts and tables are parsed once instead of on every data row or pass. - Template editor: turning the group or the total summary of a table off and on again in the table editor now restores the properties of `group`, `group.summary` and `totalSummary` that the editor does not manage (they were lost when the object was removed); the same for a summary that lost all its cells and got some again. - Template editor: the *Load template* dialog closed with the cross in its header no longer leaves the modal overlay behind (it blocked all clicks) and can be opened again; the dialog visibility is now bound two-way (`@bind-Visible`). - Template editor: after a node is deleted, the next sibling (or the previous one, or the parent only when there is no sibling) is selected instead of the parent, so pressing Delete again no longer removes the whole container with its children. - Schema: `PropertySchema.ColorFormat` (additive; the `colorFormat` property of `template-schema.json`) tells whether the format of a `color` property is validated: `hex` (the default when missing) or `unchecked` (`Chart.series.color`, which OxyPlot reads on its own and the validation checks with a warning); the descriptions of `Line.color` and `Chart.series.color` list the accepted notations. - Charts: a series or palette color for which OxyPlot throws `OverflowException` instead of `FormatException` (a hex notation that is too long such as `#FFFFFFFFF`, a number out of range such as `256,0,0` or `-1,0,0`) no longer fails the render of the chart; like every other unreadable color it falls back to `SteelBlue` (all colors of a chart are read through the new internal `ChartColors.TryParse`). The validation warns about such colors (`NRP029`, a warning in both modes). - Rendering: `RenderOptions.ValidationMode` (default `Strict`, so nothing changes) lets a caller render a template with `Compat` validation: problems that 1.2.0 started to reject as errors (unknown style property, wrong type, invalid enum or color, unknown node property) are warnings and the template renders as it did before. `ParseCompletedContext.Diagnostics` (new, additive) delivers the parse diagnostics (warnings) to the pipeline observer in both modes, and `ReportRenderer` logs them as one warning in `Compat`. `Compat` does not guarantee that the template renders: a value the renderer cannot accept (e.g. an invalid style color in PDF) still fails when the output is generated. - Rendering: `RenderOptions.OnBindingDiagnostics` (new `BindingDiagnosticsCallback` delegate, additive) delivers the binding diagnostics of one render to the caller without replacing the pipeline observer (an observer passed to `RenderAsync` replaces the one from the constructor/DI, the callback does not): it is called once after the render finished, also after a failed one (with what was collected up to the failure, empty for a parse error), and an exception thrown by it is logged and does not change the result of the render. - MCP server: `validate_data` and `validate_data_files` return the binding diagnostics of the render (`bindingDiagnostics`, the same entries as `render_report`), and a binding error makes `success=false` with an `error` message (before, only an exception of the render did; the prompt already said "fix binding problems until success=true"). Binding warnings do not fail the validation; a missing data field is not a binding problem and is not reported. - Validation: a margin or padding property (`marginMm`, `paddingTopMm`, ...) in the inline style of a paragraph span (`spans[].style`) now gives the warning `NRP030` (`DiagnosticCodes.SpanLayoutStyleIgnored`, a warning in both modes): PDF and SVG render only the text properties of a span and ignore it, HTML turns it into CSS of the span, so the outputs differed silently. A `styleRef` to a named style with such properties is not checked. - Template editor: quick consecutive edits of the same node with the same editor (the table or chart editor, the node property grid; each within 2 seconds of the previous one) are now one Undo step instead of one step per edit, so repeated clicking in the table editor no longer uses up the 50 steps of the history; Undo returns the state before the first edit of the series (`TemplateChange.GroupKey`, `TemplateHistory.CoalesceWindow`). - Template editor: the Preview tab now shows the binding errors of the template texts (an unterminated `{{`, an empty `{{}}`, an invalid C# expression) with their JSON path in the panel "Chyby bindingů v textech (z náhledu)" (`PreviewService.PreviewResult.BindingErrors`, collected through `RenderOptions.OnBindingDiagnostics`); before, such errors were invisible in the editor. Binding warnings are not shown: the preview runs over empty data, so they would only report the missing data (for example every chart). - Dependencies: removed the unused `SkiaSharp.Svg` 1.60.0 (with its transitive `SkiaSharp` 1.60.0, whose `win7-x64`/`win7-x86` runtimes caused the NETSDK1206 warning in every project; no code used it and the charts chapter says Skia measuring is intentionally not used) from the NuGet package. Other updates for known vulnerabilities and missing versions: AngleSharp 1.4.0 -> 1.8.3 (template editor), Microsoft.AspNetCore.OpenApi 10.0.3 -> 10.0.12 with Microsoft.OpenApi 2.12 (ReportServer API), AWSSDK.Core pinned to 4.0.102.8 (ReportServer core), AspNetCore.HealthChecks.UI 8.0.2 -> 9.0.0 and KubernetesClient pinned to 17.0.14 (ReportServer UI). The solution builds without warnings and `dotnet list package --vulnerable --include-transitive` reports nothing. - Validation: nodes that the AST builder cannot build are now reported with their JSON path and node id (an error in both modes) instead of being dropped silently - and because a parent with an unbuilt child is dropped too, one such node used to remove its whole subtree up to the section root (for `content` the template failed to build without a single diagnostic, in an optional section like `pageFooter` the section silently vanished): an empty required `Image.src`, `HttpLink.text`/`url`, `Barcode.value`, `Code2D.value`, `Checkbox.value` or `Chart.source` (`NRP011`), an incomplete `repeat` (empty or missing `source` or `as`: the repetition used to be ignored silently and the node rendered once; `NRP011`), an `Absolute.zIndex` that is not an integer in the Int32 range such as `1.5` (`NRP014`) and a `Row.columns` number out of the `decimal` range (`NRP014`). - Template editor: the template in progress is kept as a draft in the browser (`localStorage`, written 1.5 s after the last change), and a new circuit offers to restore it ("Obnovit" / "Zahodit") instead of silently starting with the default template - after a network loss, a pod restart or an expired Blazor circuit the work in progress used to be lost (the Undo history of the lost circuit still is). Saving to the server, loading, uploading and Reset clear the draft; only unsaved work is offered (`TemplateDraftStore`). - Template editor: the chart editor model (mapping of the chart node to and from JSON, the rules by chart type, series and palette operations) was extracted from the `ChartEditor` component into the public `ChartEditorModel` with tests, like the table editor model before; a series, palette or size value outside the `decimal` range no longer throws when the chart is loaded. - Rendering: a `Line` without `color` now uses the `color` of its style (`styles.base`, `styleRef`, inline `style`) as documented, and black only when the style has none. Before, the schema default `#000000` of `Line.color` was filled in before the build, so the color of the style was never used (the fallback in the renderers was unreachable); the default was removed from `template-schema.json`. A template whose style has a `color` and that has lines without their own `color` now draws those lines in that color instead of black; set the `color` of the line to `#000000` to keep it black. - Dependencies: QuestPDF 2025.12.3 -> 2026.9.1. This fixes the concurrent generation bug of QuestPDF (silently corrupted PDF/SVG output when documents are generated in parallel in one process), so the process-wide lock around `GeneratePdf`/`GenerateSvg` introduced in 1.2.0 is removed and PDF/SVG rendering is parallel again (`ConcurrentRenderTests` stay as a guard; they failed on 2025.12.3 and 2026.8.0 and pass on 2026.9). QuestPDF 2026.9 changed the font defaults (system fonts off, an unavailable font family or a missing glyph stops the generation), so `ReportRenderer` sets `UseSystemFonts = true`, `ThrowOnMissingFontFamilies = false` and `ThrowOnMissingTextGlyphs = false` at the first render to keep the behavior of the earlier versions (a template that uses a font that is not installed, for example `Inter` in a container, is rendered with the built-in Lato instead of failing). These are process-wide QuestPDF settings. The binary output of PDF files changed with the new QuestPDF version. - ReportServer: binding diagnostics of a render are now recorded on the render job (new nullable `text` column `RenderJobs.BindingDiagnosticsJson`, EF migration `AddRenderJobBindingDiagnostics`, applied when the API starts). The API collects them through `RenderOptions.OnBindingDiagnostics` (merged, at most 50 distinct, message cut to 1000 and JSON path to 500 characters) and returns them from the job detail (`GET /render/jobs/{id}`, `/render/jobs/last`, `/render/jobs/users/{userId}/last`: `bindingDiagnostics` with `severity`, `message`, `jsonPath`, and `bindingDiagnosticsOmitted`); the job lists return only the counts `bindingDiagnosticCount` and `bindingErrorCount`. An empty array means none, `null` means not recorded (a job from before the column, or a render that failed before bindings were evaluated; a failed render stores diagnostics only when it collected some). A cache hit takes the diagnostics of the original job (the same input gives the same diagnostics). Every render response now carries the header `X-Render-Job-Id` (the new cache-hit job for a cache hit; also on an error response once the job exists; exposed in the UI CORS policy) so that clients can read the diagnostics of exactly that job. - MCP server: `render_template` returns `bindingDiagnostics` (read from the recorded diagnostics of the ReportServer job; before, always `null` because the render ran in ReportServer) and the new field `jobId` (ReportServer render job id, to be used with `get_render_job` / `get_render_job_pdf`); `get_render_job` returns `bindingDiagnostics` and `bindingDiagnosticsOmitted`, `list_render_jobs` the counts `bindingDiagnosticCount` and `bindingErrorCount`. When the job cannot be read (or has no recorded diagnostics) `bindingDiagnostics` stays `null` and the render does not fail. - ReportServer UI: the Render page shows the binding diagnostics of the rendered job in a warning box, the Jobs page has the column "Bindingy" (count, red when there is an error; a tick when there are none) and lists the diagnostics in the detail of the user's own jobs (the detail of another user's job, which an admin sees, shows only the count), the Diagnostics page shows the count; the list is the new shared component `BindingDiagnosticsList`. - Fix (ReportServer): an exception message longer than the column `RenderJobs.ErrorMessage` (2000 characters, for example `DocumentLayoutException` of QuestPDF, whose message describes the whole layout) made saving the failed render throw `DbUpdateException`: the job stayed in the state Running and the client got an unhandled HTTP 500 instead of `RENDER_FAILED`. The stored message is now cut to the column length (ending with an ellipsis). - Fix (ReportServer UI): `AspNetCore.HealthChecks.UI` 9.0.0 references the assembly `IdentityModel` without declaring the dependency; it used to come with `KubernetesClient` 15.0.1, which the previous dependency update replaced by 17.0.14 (no longer depends on it), so the health collector of the dashboard `/health-ui` threw `FileNotFoundException` on every cycle and showed nothing. `IdentityModel` 5.2.0 is now referenced explicitly. Celý seznam změn: CHANGELOG.md v balíčku a https://dev.azure.com/advsoft/Knihovny/_git/NetReporter?path=/src/NetReporter/CHANGELOG.md