-
Notifications
You must be signed in to change notification settings - Fork 0
Fiddle: update to latest ui-react #14
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -50,6 +50,7 @@ export function Dropzone(props: IDropzoneProps): React.ReactElement { | |||||
| style={style} | ||||||
| > | ||||||
| <input | ||||||
| ref={(inputProps as React.InputHTMLAttributes<HTMLInputElement> & { ref?: React.Ref<HTMLInputElement> }).ref} | ||||||
|
||||||
| ref={(inputProps as React.InputHTMLAttributes<HTMLInputElement> & { ref?: React.Ref<HTMLInputElement> }).ref} | |
| ref={inputProps.ref} |
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 version specifier has been changed from a pinned version
0.11.3-next.18to a caret range^0.11.3-next.22. This changes the versioning strategy for this devDependency.For pre-release versions (versions with
-next), npm's caret behavior might not work as expected. The caret (^) allows updates that do not modify the left-most non-zero element, but with pre-release identifiers, the behavior can be unpredictable. Consider whether you want to:^) for consistent builds~) to allow only patch-level changesThis change should also be reflected in the peerDependencies constraint on line 49, which currently specifies
>=0.11.3-next.18.