UI5 / UI5/webcomponents

[MultiInput] Add support for loading state

Open
#12,254 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Design Pending feature request Medium Prio SAP Signavio TOPIC RL
Dominant language
TypeScript
Stars
1.8k
Forks
285
Avg merge
3d 2h
Merged PRs (30d)
59

Description

Is your feature request related to a problem?

The MultiInput component does not have a loading state and the user is required to implement one.

Describe the solution you'd like

While working on an issue relating to the content of the MultiInput not showing when fetching data, I realised that the component does not provide a native loading state. The effect of this is that the consumer of the component is required to implement a loading indicator of some sort and potentially leads to introducing custom styling outside of the Ui5 library.
I propose that this loading state should be natively supported by the MultiInput out-of-the box via a prop or a boolean value.

Describe alternatives you've considered

I tried using the <BusyIndicator /> to manually implement a loading state

Additional Context

No response

Organization

SAP

Declaration
  • I’m not disclosing any internal or sensitive information.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the MultiInput component entry point and reviewing how its current content and BusyIndicator-related behavior are implemented. Define the loading API and its expected visual behavior, then add the relevant component coverage so the work is complete when MultiInput natively exposes and reflects a loading state.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.