Fixing Kubernetes Kit documentation error for V24

articles/_vaadin-version.adoc

@@ -1,5 +1,5 @@
 ---
-:vaadin-version: 24.3.2
-:vaadin-flow-version: 24.3.2
+:vaadin-version: 24.3.9
+:vaadin-flow-version: 24.3.8
 :vaadin-seven-version: 7.7.38
 :vaadin-eight-version: 8.20.0

articles/advanced/i18n-localization.asciidoc

@@ -4,14 +4,18 @@ description: Implementing localization and translation strings using I18NProvide
 order: 20
 ---
 
-= [since:com.vaadin:vaadin@V24.3]#Localization#
+
+= Localization
 
 To use localization and translation strings, the application needs only to have the translation properties available on the classpath under the directory, `vaadin-i18n` with the filename prefix, `translations` (e.g., `src/main/resources/vaadin-i18n/translations.properties`).
 
 When using localization in an application, calling for a translation, or when the I18NProvider is used for the first time, the folder resource, `vaadin-i18n` is checked if it contains any `translations.properties` or `translations_[langcode].properties` files. Any language codes are collected from the available property files and added as provided locales in the [classname]`DefaultI18NProvider`.
 
 The file `translations.properties` is a default translation file that'll be used for any [classname]`Locale` that doesn't have a specific translations file. Locale translation files are named, for example, like [filename]`translations_fi_FI.properties` or [filename]`translations_de.properties`. The automatic [classname]`Locale` creation supports from one to three parts (e.g., `translations_language_country_variant.properties`).
 
+[NOTE]
+[classname]`DefaultI18NProvider` is available as of version 24.3 of Vaadin Flow. For an earlier version, you'll need to implement your own [interfacename]`I18NProvider`, as documented in <<#defining-i18n-provider-property,Defining I18n Provider Property>> section.
+
 
 == Locale Selection for New Session
 

articles/binding-data/components-binder-load.asciidoc

@@ -127,6 +127,20 @@ If a bean-level validator fails in [methodname]`writeBean(Object)` or [methodnam
 Remember to check your `getters/setters` to ensure there are no unwanted side effects.
 
 
+== Writing as a Draft
+
+In addition to other means of writing field values to a business object, there's also a way to write the bean as a draft. This means that it's not required for all field validations to pass, and bean-level validation isn't run at all.
+
+[source,java]
+----
+// This will write all values which pass conversion and field-level validation to person bean.
+binder.writeBeanAsDraft(person);
+
+// This will write all values which pass conversion to person bean, ignoring field-level validation.
+binder.writeBeanAsDraft(person, true);
+----
+
+
 == Tracking Binding Status
 
 [classname]`Binder` keeps track of which bindings have been updated by the user and which bindings are in an invalid state.

articles/binding-data/components-binder-validation.asciidoc

@@ -147,10 +147,23 @@ departing.addValueChangeListener(
         event -> returningBinding.validate());
 ----
 
+
+=== Temporarily By-Passing Validation
+
+Validators can be by-passed temporarily on both binder-level and binding-level. In practice, this allows bean writing to succeed even when one or more validators would not pass.
+
+[source,java]
+----
+// Disables all validators, both binder-level and binding-level
+binder.setValidatorsDisabled(true);
+
+// Disables validators for a single binding
+binding.setValidatorsDisabled(true);
+----
+
 == Converting User Input
 
 You can bind application data to a UI field component, even if the types don't match.
-
 Examples where this is useful include:
 
 * an application-specific type for a postal code that the user enters in a `TextField`;

articles/compatibility.adoc

@@ -17,7 +17,7 @@ This page shows the minimum required versions of supported technologies for Vaad
 | Spring Boot| 3.0 or later
 | Node.js| 18 or later
 | Maven| 3.5 or later (except for 3.8.2 and 3.8.3)
-| Gradle| 7.5 or later
+| Gradle| 8.5 or later
 | Servlet| 6 or later
 | Application Servers
 a|
@@ -61,8 +61,11 @@ Vaadin 24 is supported by several web browsers. The following is a list of compa
 | Safari | 15 or later
 |===
 
+
+[discussion-id]`06849B4A-676D-49C6-BED2-290DD90DF57D`
+
 ++++
 <style>
 [class^=PageHeader-module--descriptionContainer] {display: none;}
 </style>
-++++
+++++

articles/components/index.asciidoc

@@ -197,7 +197,7 @@ include::message-input/index.asciidoc[tag=description]
 
 image::{components-path-prefix}multi-select-combo-box/multi-select-combo-box.png["", role="banner"]
 
-include::multi-select-combo-box/index.asciidoc[tag=description]
+include::multi-select-combo-box/index.adoc[tag=description]
 
 [.sr-only]
 <<{components-path-prefix}multi-select-combo-box#,See Multi-Select Combo Box>>
@@ -466,7 +466,7 @@ endif::[]
 
 image::{components-path-prefix}menu-bar/menu-bar.png["", opts=inline, role="banner"]
 
-include::menu-bar/index.asciidoc[tag=description]
+include::menu-bar/index.adoc[tag=description]
 
 [.sr-only]
 <<{components-path-prefix}menu-bar#,See Menu Bar>>
@@ -477,7 +477,7 @@ include::menu-bar/index.asciidoc[tag=description]
 
 image::{components-path-prefix}message-list/message-list.png["", role="banner"]
 
-include::message-list/index.asciidoc[tag=description]
+include::message-list/index.adoc[tag=description]
 
 
 [.sr-only]

articles/configuration/development-mode/dev-tools/component-locator.adoc

@@ -1,18 +1,18 @@
 ---
 title: Component Locator
-description: Use Component Locator to identify components in views and find their source code in your IDE.
+description: Use Component Locator to identify components in views and find their source code in an IDE.
 order: 1
 ---
 
 
 = [since:com.vaadin:vaadin@V24]#Component Locator#
 
-You can use the component locator to identify components and to find their code when running applications in <<../#,development mode>>. The component locator opens the corresponding source code in your IDE when you click a component (for example, a Button in a view).
+You can use the component locator to identify components, and to find their code when running applications in <<../#,development mode>>. The component locator opens the corresponding source code in your IDE when you click a component (e.g., a Button in a view).
 
 
 == Enabling Component Locator
 
-Start by running your Vaadin application project in development mode. Click on the Vaadin symbol [guilabel]*}>* at the bottom right-hand corner of your browser window -- as indicated in the screenshot here.
+Start by running your Vaadin Flow application project in development mode. Click on the Vaadin symbol [guilabel]*}>* at the bottom right-hand corner of your browser window -- as indicated in the screenshot here.
 
 [.device]
 image::/images/dev-tools-location.png[The Vaadin symbol location in development mode.]
@@ -25,7 +25,7 @@ image::/images/code-menu.png[The Code tab viewed in the Dev tools menu.]
 
 == Using Component Locator
 
-Now that the Component Locator has been enabled, you're ready to use it. To highlight a component in red and identify it, hover your pointer over one in the view. The component names appear in a list at the bottom right-hand corner of your browser window. You can use the arrow keys to navigate that list.
+Now that the Component Locator has been enabled, it's ready to be used. To highlight a component in red and identify it, hover your pointer over one in the view. The component names appear in a list at the bottom right-hand corner of your browser window. You can use the arrow keys to navigate that list.
 
 [.device]
 image::/images/component-locator.png[Component Locator highlighting and identifying the Button component.]
@@ -39,3 +39,17 @@ image::/images/code-view.png[The Button component and corresponding source code.
 [class^=PageHeader-module--descriptionContainer] {display: none;}
 </style>
 ++++
+
+
+[since:com.vaadin:vaadin@V24.4]
+== Disable Component Tracking
+
+Component tracking isn't an expensive operation, but it may at times be useful to disable it. Be aware that with component tracking disabled, the Component Locator tool cannot identify any components. To disable tracking, set the `vaadin.devmode.componentTracker.enabled` configuration parameter to `false`.
+See <<{articles}/configuration/properties#,Configuration Properties>> for more information about setting configuration parameters.
+
+
+++++
+<style>
+[class^=PageHeader-module--descriptionContainer] {display: none;}
+</style>
+++++

articles/configuration/development-mode/dev-tools/index.adoc

@@ -1,6 +1,6 @@
 ---
 title: Development Tools
-description: Vaadin tools that are available when running applications in development mode.
+description: Vaadin tools available when running applications in development mode.
 order: 209
 ---
 
@@ -9,6 +9,11 @@ order: 209
 
 Boost productivity with the Vaadin Development Tools, such as Component Locator, that are available when running applications in development mode.
 
+Current and future functionality of Vaadin Development Tools may offer developers ways to alter the application configuration or even application code. Therefore, it may not be desirable to enable access to Development Tools for everyone -- even when running an application in development mode.
+
+By default, Development Tools can be accessed only from loopback addresses. To configure hosts for Development Tools access, please see `devmode.hostsAllowed` <<{articles}/configuration/properties/#properties,configuration property>>.
+
+
 == Topics
 
 section_outline::[]

articles/configuration/properties.adoc

@@ -7,7 +7,7 @@ order: 10
 
 = Configuration Properties
 
-You can change the behavior of Vaadin applications by setting the configuration properties. You can use either system properties, or servlet initialization parameters to set them. See the <<properties,full list of properties>> for details.
+You can change the behavior of Vaadin applications by setting the configuration properties. You can set them either through the system properties, or the servlet initialization parameters. See the <<properties,full list of properties>> for details.
 
 See also the <<{articles}/integrations/spring/configuration#, Spring-specific instructions>> for Spring-based applications.
 
@@ -96,7 +96,6 @@ When a system property and a servlet parameter have the same name, the system pr
 
 The following table contains the properties that are defined in the [classname]`com.vaadin.server.DeploymentConfiguration` and [classname]`com.vaadin.server.Constants` classes. They're listed in alphabetical order. If you use Spring Boot, you should add the `vaadin.` prefix to them (e.g., change `brotli` to `vaadin.brotli`).
 
-
 [cols="1,1,4"]
 |===
 |Property Name |Default Value |Description
@@ -109,6 +108,10 @@ The following table contains the properties that are defined in the [classname]`
 |`false`
 |Closes the Vaadin session if no UI is active. A UI is considered active if it's open on the client-side and has any activity -- besides heartbeat requests. By default, heartbeat requests keep the Vaadin session open even when there is no user interaction. Set to `true` to close idle sessions. See `heartbeatInterval` below.
 
+|`devmode.hostsAllowed`
+|`null`
+|Defines the hosts allowed to access Vaadin development tools. A comma-separated list of allowed hosts should be provided as the value. The `?` and `\*` wildcards can be used (e.g., `192.168.1.*,172.17.?.*`). Loopback addresses are always allowed, regardless of the value set here.
+
 |`devmode.liveReload.enabled`
 |`true`
 |Enables live reload. When using a server-side <<live-reload/index#, live reload tool>>, the browser is refreshed after code is rebuilt on the server. Set to `false` to disable automatic reloading of the browser. This applies only to development mode.
@@ -121,6 +124,10 @@ The following table contains the properties that are defined in the [classname]`
 |`false`
 |Enables session serialization. When session serialization is enabled, [classname]`UI` instances and registered [classname]`StreamResource` instances are serialized or deserialized when restarting the development server. When set to `true`, for example, access control information can be preserved during development so that you don't need to log in for each change. This applies only to development mode.
 
+|`devmode.componentTracker.enabled`
+|`true`
+|Enables the <<development-mode/dev-tools/component-locator#, Component Locator>> tracker utility. Set to `false` to disable. With it disabled, the Component Locator tool cannot identify any components. This applies only to development mode.
+
 |`devmode.usageStatistics.enabled`
 |`true`
 |Enables Vaadin to collect usage statistics that can guide further development. Statistics are collected based on features that are used in the application. No data is collected in production mode. Some usage statistics are collected through the web browser. See the https://github.com/vaadin/vaadin-usage-statistics[client-side collector repository] for instructions on how to opt out. This applies only to development mode.

articles/contributing/docs/styleguide.adoc

@@ -321,7 +321,7 @@ Avoid ending a sentence with an exclamation mark. Its use in normal text is dist
 
 Don't pose a question in the text; don't end a sentence with a question mark. You're not in dialog with the reader, so don't ask them a question when you can't hear their response. That's potentially irritating to the reader. Instead, write what you want to say without questions. The exception to posing a question and using a question mark is for titles of troubleshooting articles.
 
-The use of ellipses (i.e., ⋮) at the end of a sentence, usually an incomplete sentence, is meant to indicate that the writer is thinking or calling upon the reader to ponder something. Write complete sentences; write what you want to say. Don't require the reader to wonder what you're thinking. Ellipses sometimes can be used in the same way in the middle of a sentence. They're also sometimes used in lieu of etc. Again, don't use them.
+The use of ellipses (i.e., …) at the end of a sentence, usually an incomplete sentence, is meant to indicate that the writer is thinking or calling upon the reader to ponder something. Write complete sentences; write what you want to say. Don't require the reader to wonder what you're thinking. Ellipses sometimes can be used in the same way in the middle of a sentence. They're also sometimes used in lieu of etc. Again, don't use them.
 
 These three punctuation rules don't apply to using them as part of some code syntax or code example. They apply only to sentences and headings. Ellipses are sometimes used in code or log examples in place of lengthy, unimportant text. This is an acceptable use.
 
@@ -492,6 +492,9 @@ Call `setEnabled(false)` to disable it.
 // TODO source-code
 
 
+
+[discussion-id]`FAAF4D05-ED0A-4D13-A416-C8033BACC6A3`
+
 ++++
 <style>
 [class^=PageHeader-module--descriptionContainer] {display: none;}

articles/contributing/docs/vale.adoc

@@ -79,6 +79,8 @@ pass:[<!-- vale Vaadin.Will = YES -->]
 Rules that use `scope: raw` (e.g., `Vaadin.SourceCode`) can't be suppressed with these comments.
 
 
+[discussion-id]`B8CB88DA-F241-4F01-BEDE-22C4AEA6F4AC`
+
 ++++
 <style>
 [class^=PageHeader-module--descriptionContainer] {display: none;}

articles/contributing/pr.adoc

@@ -132,6 +132,9 @@ If the PR isn't approved by the reviewer and there is no response from the autho
 
 Another aspect to consider is that, as time passes, more and more new features and fixes are merged into the `main` branch. As a result, the more a PR is waiting to be merged, the higher the probability of merge conflicts. Such conflicts must be resolved before the merge.
 
+
+[discussion-id]`72291A8F-D77D-4730-B035-7D548AF8DA4D`
+
 ++++
 <style>
 [class^=PageHeader-module--descriptionContainer] {display: none;}

articles/contributing/tests.adoc

@@ -313,8 +313,10 @@ If possible, avoid asynchronous tests. It simplifies reviewing of the test and h
 Keep in mind that there could be differences in browsers behaviour, so it's a good habit to check that tests pass on all supported browsers. Supported browsers are listed in the release notes of each Vaadin major and minor release: https://github.com/vaadin/platform/releases
 
 
+[discussion-id]`77BC1B54-F570-41CD-96A5-4DC80E437C83`
+
 ++++
 <style>
 [class^=PageHeader-module--descriptionContainer] {display: none;}
 </style>
-++++
+++++