Custom Component support for Hilla

[emarc]

Description

For custom components and composites, Hilla needs a similar set of features as Flow.

Tier

Plus

License

Proprietary

Motivation

Background

Custom components and composites are essentially all components included in the project that are not part of the basic OOTB Vaadin component set.

In 24.7 we released improvements for how custom components / composites are handled in Flow.
For 24.8 we’re improving that support.
We also need the same type of support for Hilla.

Problem

Custom components are defined in separate files and can be shared throughout the project.
Custom components and composites have custom API and custom “slots”/areas for components.
Copilot needs to clearly show what is being edited so shared files are not accidentally changed. When there are limitations, those need to be indicated.

Hilla needs to match the functionality provided for Flow, including drag & drop, drill-down, Properties editor, AI, etc.

Solution

Match the features in Flow, taking into consideration that not all features exist in the same way.

Notes

Hilla/React works differently especially regarding properties, drops “slots”, and inheritance.
While the user needs are similar, the concepts differ.

Requirements

• Feature parity with Flow support

• Documentation (potential differences Hilla vs Flow)

• License check

Nice-to-haves

Risks, limitations and breaking changes

Risks

Hilla differs from Flow wrt "custom components" – some features may not get "parity".

Limitations

Not 100% parity.

Breaking changes

(no breaking changes expected)

Out of scope

No response

Materials

No response

Metrics

No response

Pre-implementation checklist

• Estimated (estimate entered into Estimate custom field)
• Product Manager sign-off
• Engineering Manager sign-off

Pre-release checklist

• Documented (link to documentation provided in sub-issue or comment)
• UX/DX tests conducted and blockers addressed
• Approved for release by Product Manager

Security review

None