We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
fastjson1升fastjson2时,使用的是Fastjson v1兼容模块 <dependency> <groupId>com.alibaba</groupId> <artifactId>fastjson</artifactId> <version>2.0.50</version> </dependency>
出现以下问题
String json = "{0:12,1:13,2:14,\"date\":\"2024-05-14\"}"; Map<Object,Object> map = JSON.parseObject(json, Map.class);
fastjson1取值如下: Integer date0 = (Integer) map.get(0);// 取到值为12 Integer date1 = (Integer) map.get(1);// 取到值为13
fastjson2用com.alibaba.fastjson.JSON取值如下: Integer date0 = (Integer) map.get(0);// 取到值为null Integer date1 = (Integer) map.get(1);// 取到值为13
fastjson2下得到的date0是不对的,发现fastjson2把key为0转成了字符串,但key为1又还是整数,这也太奇怪了。
The text was updated successfully, but these errors were encountered:
fix zero or negative number key map deserialize, for issue #2570
ff2a1a3
https://oss.sonatype.org/content/repositories/snapshots/com/alibaba/fastjson/2.0.51-SNAPSHOT/ 问题已修复,请帮忙用2.0.51-SNAPSHOT版本验证下
Sorry, something went wrong.
https://github.com/alibaba/fastjson2/releases/tag/2.0.51 问题已修复,请用新版本
No branches or pull requests
fastjson1升fastjson2时,使用的是Fastjson v1兼容模块
<dependency>
<groupId>com.alibaba</groupId>
<artifactId>fastjson</artifactId>
<version>2.0.50</version>
</dependency>
出现以下问题
String json = "{0:12,1:13,2:14,\"date\":\"2024-05-14\"}";
Map<Object,Object> map = JSON.parseObject(json, Map.class);
fastjson1取值如下:
Integer date0 = (Integer) map.get(0);// 取到值为12
Integer date1 = (Integer) map.get(1);// 取到值为13
fastjson2用com.alibaba.fastjson.JSON取值如下:
Integer date0 = (Integer) map.get(0);// 取到值为null
Integer date1 = (Integer) map.get(1);// 取到值为13
fastjson2下得到的date0是不对的,发现fastjson2把key为0转成了字符串,但key为1又还是整数,这也太奇怪了。
The text was updated successfully, but these errors were encountered: