Skip to content
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.

Sign up for GitHub

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

Jump to bottom

JQMIGRATE: jQuery.parseJSON is deprecated; use JSON.parse #102

Open
mukaofssn opened this issue Oct 5, 2018 · 5 comments
Open

JQMIGRATE: jQuery.parseJSON is deprecated; use JSON.parse #102

mukaofssn opened this issue Oct 5, 2018 · 5 comments
Labels
1 - Ready bug cost: S Will take up to 2 days to complete PRI: 1 - Required Must be handled in a reasonable time
Milestone
4.0.1

Comments

@mukaofssn
Copy link

While upgrading JQuery to 3.3.1, jquery.validate.unobtrusive.js to 3.2.10 along with JQuery Migrate 3.0.0, the above warning shows up. Kindly advise if this will be addressed in the coming versions.
@mkArtakMSFT
Copy link
Member

Thanks for contacting us, @mukaofssn.
Can you please share a sample repro project so we can investigate it?

@mkArtakMSFT mkArtakMSFT added investigate bug 1 - Ready PRI: 1 - Required Must be handled in a reasonable time and removed investigate labels Oct 5, 2018
@mkArtakMSFT mkArtakMSFT added this to the 3.2.12 milestone Oct 8, 2018
@ryanbrandenburg ryanbrandenburg added the cost: S Will take up to 2 days to complete label Mar 8, 2019
@RobJohnston
Copy link

Link to upstream issue: jquery-validation/jquery-validation#2322

@mukaofssn
Copy link
Author

@mkArtakMSFT my apologies I completely missed your reply and just now got an email reminder to share a repro code.

@neilmulhy
Copy link

Any news when v3.2.13 is out and whether this issue will be fixed in it? I'm looking to upgrade to JQuery v3.6 but the latest CDN (v3.2.12) doesn't have the fix in -> https://cdnjs.cloudflare.com/ajax/libs/jquery-validation-unobtrusive/3.2.12/jquery.validate.unobtrusive.js

@mkArtakMSFT mkArtakMSFT modified the milestones: 3.2.12, 4.0.1 Jul 20, 2022
@RobJohnston RobJohnston mentioned this issue Jan 14, 2023
Merged
@gplwhite
Copy link

While the PR #161 has been merged, a new release hasn't been published which means this fix isn't available in any downstream package managers.

Any chance a new release (maybe 4.1.0??) could be published to fully resolve this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
1 - Ready bug cost: S Will take up to 2 days to complete PRI: 1 - Required Must be handled in a reasonable time
Projects
None yet
Milestone
4.0.1
Development

No branches or pull requests
6 participants
@gplwhite @RobJohnston @ryanbrandenburg @mukaofssn @neilmulhy @mkArtakMSFT