Merge branch 'main' into issues/5358-improve_test_with_selenium_page

Author: caalador

articles/_vaadin-version.adoc

@@ -1,7 +1,7 @@
-:vaadin-version: 25.1.0
+:vaadin-version: 25.1.1
 :vaadin-start-platform-version: v25.1
 :vaadin-start-java-version: 21
-:vaadin-flow-version: 25.1.0
+:vaadin-flow-version: 25.1.1
 :vaadin-seven-version: 7.7.49
 :vaadin-eight-version: 8.28.4
 :spring-boot-version: 4.0.4

articles/components/grid/renderers.adoc

@@ -217,6 +217,33 @@ grid.addColumn(
              () -> VaadinIcon.ARROW_LEFT.create()));
 ----
 
+Component renderers allow providing an optional update function that can be used to optimize rendering.
+Without an update function, component renderers recreate components for each item whenever the grid needs to be refreshed.
+This has several downsides:
+
+* It results in a large number of DOM changes in the browser as old elements are removed and new ones are added
+* It results in a larger payload that needs to be sent to the browser
+* Components lose their client-side state, for example, input fields lose their focus or entered text that has not been committed
+
+By providing an update function, the grid can reuse existing components and only update their state. This results in fewer DOM changes, smaller payloads, and better user experience.
+
+The following example shows how to provide an update function to a component renderer:
+
+[source,java]
+----
+grid.addColumn(new ComponentRenderer<>(item -> {
+    // Create the initial component using item name as text
+    return new Badge(item.getName());
+}, (component, item) -> {
+    // Update the component text when the item changes.
+    // Cast is necessary as component renderer is typed
+    // so that it allows the update function to return 
+    // a different component type if desired.
+    ((Badge) component).setText(item.getName());
+    return component;
+}));
+----
+
 You can create complex content for the grid cells by using the component APIs. This example is using [classname]`ComponentRenderer` to create complex content that listens for events and wraps multiple components in layouts:
 
 [source,java]

articles/styling/index.adoc

@@ -46,7 +46,11 @@ The Vaadin 24 way of loading styles through the [annotationname]`@Theme` annotat
 
 == Themes
 
-By default, Vaadin components are rendered with their minimalistic built-in <<themes/base#, base styles>>, which are a good starting point if you want to customize the look and feel extensively. Vaadin also ships with two themes, <<themes/aura#, Aura>> and <<themes/lumo#, Lumo>>, that provide a more polished look and feel for Vaadin components.
+Vaadin components come bundled only with minimalistic, built-in base styles, on top of which the application can load one of the two Vaadin themes, <<themes/aura#, Aura>> or <<themes/lumo#, Lumo>>, which provide a more polished look and feel.
+
+If no [interfacename]`AppShellConfigurator` is defined for the application, the Aura theme will be loaded automatically. Otherwise either theme needs to be loaded explicitly using the [annotationname]`@StyleSheet` annotation.
+
+While both themes are highly customizable, you can also choose to implement your own custom styling directly on top of the <<themes/base#, base styles>> in order to avoid having to override the styling provided by the theme.
 
 [cols="^.^1, ^.^1, ^.^1"]
 |===

articles/tools/modernization-toolkit/swing-bridge.adoc

@@ -129,7 +129,7 @@ Add the following parent section, properties, and dependencies to your `pom.xml`
 <parent>
   <groupId>org.springframework.boot</groupId>
   <artifactId>spring-boot-starter-parent</artifactId>
-  <version>4.0.3</version>
+  <version>4.0.4</version>
   <relativePath/>
 </parent>
 
@@ -142,13 +142,6 @@ Add the following parent section, properties, and dependencies to your `pom.xml`
       <type>pom</type>
       <scope>import</scope>
     </dependency>
-    <dependency>
-        <groupId>tools.jackson</groupId>
-        <artifactId>jackson-bom</artifactId>
-        <version>3.1.0</version>
-        <type>pom</type>
-        <scope>import</scope>
-    </dependency>
   </dependencies>
 </dependencyManagement>
 

dspublisher/dspublisher-scripts.js

@@ -187,7 +187,7 @@ const SCRIPTS = {
             lastPhase: true,
           },
         ],
-        ignoredLogSignals: ['New version of Astro available'],
+        ignoredLogSignals: ['New version of Astro available', 'Observability agent is not running'],
       },
     ].filter((p) => !!p),
   },