-
Notifications
You must be signed in to change notification settings - Fork 921
fix(FileUpload): ensure native validation works with required #5358
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
benjamincanac
wants to merge
2
commits into
v4
Choose a base branch
from
pr/5210
base: v4
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+139
β124
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The exposed
inputRefanddropzoneRefhave inconsistent access patterns.inputRefis a getter returning a DOM element directly, whiledropzoneRefremains a ref requiring.valueaccess. This breaks backward compatibility and creates an inconsistent API.View Details
Analysis
FileUpload component has inconsistent ref exposure patterns breaking API consistency
What fails: FileUpload.vue
defineExposeexposesinputRefas getter returning DOM element directly, whiledropzoneRefremains a ref, creating inconsistent access patterns that break established component API conventions.How to reproduce:
Expected behavior: Both refs should be exposed consistently. Example usage in
InputKbdExample.vueshows expected pattern:input.value?.inputRef?.focus()which works with Input component but would break with FileUpload's inconsistent exposure.Result: FileUpload breaks the established pattern used by Input, Textarea, and Select components which all expose refs directly via
defineExpose({ inputRef }), while FileUpload uses a getter that bypasses the ref wrapper.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@benjamincanac This suggested change makes sense, but it would introduce a breaking change π¬ Seems minor enough to accept it tho?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No it is incorrect, the
inputRefis now bound on a Vue component (VisuallyHidden) which adds a layer over binding directly to an<input>: https://vuejs.org/guide/essentials/template-refs.html#ref-on-component. We need to return$elto access the actual input as before.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we wrap it inside a computed instead to ensure that it is reactive?