From a11d3960abdd3b2bc93845e0a2e1311a3846eb48 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Petter=20Holmstr=C3=B6m?= Date: Mon, 16 Dec 2024 12:56:10 +0200 Subject: [PATCH] Vale override --- articles/hilla/lit/guides/upgrading/index.adoc | 3 +++ 1 file changed, 3 insertions(+) diff --git a/articles/hilla/lit/guides/upgrading/index.adoc b/articles/hilla/lit/guides/upgrading/index.adoc index 8be0d4a06b..9dba15d781 100644 --- a/articles/hilla/lit/guides/upgrading/index.adoc +++ b/articles/hilla/lit/guides/upgrading/index.adoc @@ -725,11 +725,14 @@ The behavior of null type annotations, such as `@com.vaadin.hilla.Nonnull`, has This also affects nullability in generated TypeScript code. Consider using the <<{articles}/hilla/lit/reference/type-nullability#nonnullapi,@NonNullApi>> annotation for declaring nullability on the package level. +// Allow Vaadin Components in header +pass:[] === Breaking Changes in Vaadin Components Upgrading a Hilla application to Hilla 2 can involve several breaking changes. They're described in the following sub-sections. +pass:[] ==== Behavior & Styling