h2oai / h2oai/wave

Semantic validation for ui.components

Open
#1,493 0 comments 0 reactions 0 assignees View on GitHub
devx feature
Dominant language
Python
Stars
4.3k
Forks
371
Avg merge
26d 1h
Merged PRs (30d)
1

Description

#### Is your feature request related to a problem? Please describe

For some ui components such as `ui.notification_bar` you can specify `events`. This is only working if also a `name` property is given, which is optional otherwise. If a name is not provided, the events are not catched and the root cause is unclear (fails silently).

#### Describe the solution you'd like

Warning the user about a missing parameter or mutually exclusive parameters would speed up debugging and development. This could be done by some kind of semantic validation, either at component input or in the IDE tools.

#### Describe alternatives you've considered

Check in the ui.component
Check through the IDE plugins

Contributor guide

Open the contributing guide

Research direction

Start by examining ui.component and the IDE plugins to determine where component inputs are currently checked. Define how missing name and the events/name relationship should be reported, then verify that invalid ui.notification_bar configurations produce a clear warning instead of failing silently.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.