| This is the talk page for discussing improvements to the JSON article. This is not a forum for general discussion of the subject of the article. |
Article policies
|
| Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
| This article is rated B-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||
The community here may be interested in reviewing and/or editing the draft article on JSONPath. Glyn normington (talk) 16:16, 24 March 2024 (UTC)
In JavaScript it is standard to use camel case for identifiers such as properties in objects. In json this not a requirement as there are not identifiers just strings. I wonder if this should be mentioned somewhere as it is important when converting objects in JSON notation to JavaScript objects and vv. Theking2 (talk) 15:11, 29 May 2024 (UTC)
| This edit request by an editor with a conflict of interest has now been answered. |
I am associated with the website onthegotools.com. I would like to propose adding a link to the JSON tools section of my website. I believe it would be a useful resource for readers looking for online tools to validate and format JSON data. Proposed link: * [https://onthegotools.com/#json-tools JSON Tools] Vimal2282 (talk) 14:15, 19 August 2025 (UTC)
Poor John with 3 children and no mom for them! Couldn't we give him a wife? He's quite lonely.
In all seriousness, this article is already amazing and this is just one small thing I think should be added. BlueHorizons314 (talk) 02:03, 6 March 2026 (UTC)
null. — W.andrea (talk) 16:56, 6 March 2026 (UTC)
Informasi ini disarikan dari Wikipedia dan disajikan kembali untuk tujuan edukasi. Konten tersedia di bawah lisensi CC BY-SA 3.0. Kami tidak bertanggung jawab atas ketidakakuratan data yang bersumber dari kontribusi publik tersebut.