What’s new in Talend Component Kit

It is now recommended to use SVG custom icons instead of PNG or built-in icons.

You can now automatically pre-configure components from the Component Kit Starter by providing a JSON OpenAPI document.

You can now include datetime options to your component configuration class by using the Java Date Time API. The following classes automatically enable the widget in your component form:

Placeholder presence is now validated if the validatePlaceholder is set to true. To ensure backward compatibility, this parameter is set to false by default.

Several enhancements were made to the Component Kit Starter:

The component-api repository has been merged into the component-runtime repository, which is now the unique GitHub repository for Talend Component Kit.

Several dependencies have been upgraded to a newer version, including:

You can now define simple queries to add filtering parameters to requests made on the /index endpoint for components and component configurations.

The Gradle plugin now supports the deploy in Studio command by default using the DeployInStudioTask.

Several dependencies have been upgraded to a newer version, including:

You can now extract data from a Record using JSON Pointer with the new RecordPointerFactory method.

The @Internationalized annotation now supports short names in Message.properties files of your projects.

Several dependencies have been upgraded to a newer version, including:

The Component Kit Starter now allows to specify datasets and datastores. Since every input and output components must rely on a dataset and that each dataset requires a datastore, you need to make sure that your project complies with the applicable validation rules to build components properly.

You can now enrich your component project with custom JAR and configuration without repackaging all applications. You can specify this customization using the new user.extensions.location parameter of the component server.

You can now manually configure the MaxBatchSize property for a component or a component family. This is especially useful when testing your components.

Several dependencies have been upgraded to a newer version, including:

Several dependencies have been upgraded to a newer version, including:

Several dependencies have been upgraded to a newer version, including:

Several dependencies have been upgraded to a newer version, including:

Every dataset must now reference a valid datastore. In addition, every input or output component must now reference a dataset.

These rules are enforced and must be respected to successfully build your components.

A validation rule now checks if custom icons are present. If not, the build will fail.

Several dependencies have been upgraded to a newer version, including:

Output components can now only have one inbound connection.

Dataset and datastore internationalized names are now validated by the Maven and Gradle plugins of the Component Kit.

In addition, a validation rule now checks that each dataset corresponds to at least one source (input component) that does not require other parameters.

It is now possible to combine several visibility conditions (ActiveIfs) using a unique operator (AND or OR).

In addition, ActiveIf now supports CONTAINS as evaluation strategy.

Internalization now supports action names.

Several dependencies have been upgraded to a newer version, including: