fix(buckets): label the allowed-file-extensions input correctly#2996
fix(buckets): label the allowed-file-extensions input correctly#2996singhvishalkr wants to merge 1 commit intoappwrite:mainfrom
Conversation
The tags input on Storage > Bucket > Settings > Allowed File Extensions was labelled as `Labels` with a placeholder of `Select or type user labels` and an id of `user-labels`. Swap all three to reflect what the field actually captures, matching the section heading (`Allowed file extensions`) and giving assistive tech a meaningful label. Fixes appwrite#2443.
Greptile SummaryThis PR fixes a copy-paste labelling issue on the Confidence Score: 5/5Safe to merge — single-file, text-only fix with no logic or behavioural changes. All three changed lines are string literals in a template; no logic, state, or API surface is affected. No P0/P1 findings. No files require special attention. Important Files Changed
Reviews (1): Last reviewed commit: "fix(buckets): label the allowed-file-ext..." | Re-trigger Greptile |
Fixes #2443.
The tags input on Storage > Bucket > Settings > Allowed File Extensions is currently rendered as:
which surfaces as
Labels/Select or type user labelsin the UI even though the field is the list of file extensions that the bucket will accept. The section heading directly above it already saysAllowed file extensionsand the surrounding state isextensions/updateAllowedExtensions, so the input is the only piece of the section still carrying the copy-paste name from an earlier labels component.This PR updates the
id,label, andplaceholderon thatInputTagsso all three match the field's purpose. No behaviour change -- only the labelling that assistive tech and the placeholder hint read.Before:
user-labels, label=Labels, placeholder=Select or type user labelsAfter:
allowed-file-extensions, label=Allowed file extensions, placeholder=Select or type file extensionsThe previous attempt at this (#2530) was closed before landing; this revision also corrects the
id/labelalongside the placeholder so screen reader / form-autofill context is consistent with the visible section.