-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Upgrade jQuery to 3.5.0, remove jQuery-Migrate, fix deprecations #11055
Conversation
@silverwind bad news: dropzone do not work anymore ... looks like it still depend on migrate :( |
It did work for me, at least adding/removing attachment. What was not working for you? |
adding attachments to a new created issue |
Will check. I did not yet run with unmuted jQuery-Migrate which should highlight all the issue in the console, but it's a bit cumbersome in general to work on issues because of SimpleMDE console spam. |
Dropzone itself claims to have no external dependencies, even jQuery... 🤔 Maybe it's the way we use it? |
Yeah, something seems fishy as we don't use the jQuery-variant of Dropzone initialization. I think the old 4.x version of Dropzone may have had a jQuery dependency, but the current version we use doesn't. |
@6543 I played around a bit with dropzone and I can't find any difference before or after this PR. Adding attachments works, there's just the non-obvious case when the attachment exceeds the file size limit (default 4mb), hitting save will still save the comment but the attachment is gone from the comment. I think it might better to just prevent save in that case. Maybe this was what you were seeing? |
no I could not use it att all - I'll recheck have cleaned test env now |
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.
works fine now
¯\_(ツ)_/¯
why it didn't before
I guess many such mysteries can be attributed to a stale service worker cache, if you have that enabled. |
Already disabled for exact that reason |
Unmuted migrate reveals a few deprecations, some in our code. I will work on eliminating them, don't land yet.
|
c0fe080
to
f23aeab
Compare
Fixed all deprecations in our code. Some still remain, but these are in dependencies or vendor files. Should be good to land now. |
- Removed jQuery-Migrate as it seems to no longer be needed. - Removed a dead code section. - Fixed some deprecations detected by jQuery-Migrate. Ref: https://jquery.com/upgrade-guide/3.5/ Ref: https://github.com/gogs/gogs/search?q=repo-name-change-prompt Ref: https://github.com/go-gitea/gitea/search?q=repo-name-change-prompt Fixes: go-gitea#9372
ping LG-TM |
…gitea#11055) - Removed jQuery-Migrate as it seems to no longer be needed. - Removed a dead code section. - Fixed some deprecations detected by jQuery-Migrate. Ref: https://jquery.com/upgrade-guide/3.5/ Ref: https://github.com/gogs/gogs/search?q=repo-name-change-prompt Ref: https://github.com/go-gitea/gitea/search?q=repo-name-change-prompt Fixes: go-gitea#9372 Co-authored-by: zeripath <art27@cantab.net>
Upgrade jQuery to 3.5.0, remove jQuery-Migrate
Ref: https://jquery.com/upgrade-guide/3.5/
Ref: https://github.com/gogs/gogs/search?q=repo-name-change-prompt
Ref: https://github.com/go-gitea/gitea/search?q=repo-name-change-prompt
Fixes: #9372