[Bug]: Required marker (*) not displayed on required select widgets

[j0hnby]

Is there an existing issue for this?

• I have searched the existing issues

Description

When setting a widget to be required to have data, the new functionality should show a red asterisk next to the title of it to inform users that it is required.

For select widget types this does not happen - images attached show "Product Category" - a required select widget with no asterisk, "Brand or Item" - a text widget which is required and the asterisk is showing, and "Model" - a text widget which is not required.

The Required option is selected in the Validations section of the widget config - I have tried toggling it to see if it was something stuck, it hasn't helped.

The validation works - the widget "isvalid" is false until it has data in it. (State shown in screenshot too)

I have tested this in Waterfox (Firefox) and Edge and it shows the same in both. I have no ad-blockers in place.

Appsmith v1.98 self hosted

Steps To Reproduce

Create UI
Add form
Add select widget - set basic details - ensure to set Validation - Required to "ON"
View form - no red required asterisk is visible for required field.

Public Sample App

No response

Environment

Production

Severity

Medium (Frustrating UX)

Issue video log

No response

Version

Self Hosted - 1.98

[linear]

APP-15123

[Arbab1308]

Confirmed: required marker appears on Text widgets but not Select/MultiSelect when Validation → Required is ON. This PR #41735 fixes it by passing isRequired into LabelWithTooltip

[Arbab1308]

@j0hnby can you please close this issue

[j0hnby]

Hi there @Arbab1308 - sure can, what release version should I be checking to verify it's done? The PR mentioned is still open and it's not in 1.99.

[Arbab1308]

Hi @j0hnby — thanks! This fix isn’t in a release yet since PR #41735 is still open (so it won’t be in 1.99).
Could we keep #41734 open for now, and close it once #41735 is merged and the fix ships in a release? I’ll ping here again after it merges.

[j0hnby]

v2.0 is released and doesn't contain this fix - do you have a projected release number that this fix will be in at all?

[Arbab1308]

i have actually closed the PR in my end i guess

[j0hnby]

Closed because of inactivity - and it says it's unmerged. This issue is still outstanding.

[Arbab1308]

how can i closed this PR

[Arbab1308]

as i have unforked and removed the repo from my github

you can handover this issue to someone else