Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/ZacHooper/mojo-json
Json Parser in Mojo
https://github.com/ZacHooper/mojo-json
Last synced: about 2 months ago
JSON representation
Json Parser in Mojo
- Host: GitHub
- URL: https://github.com/ZacHooper/mojo-json
- Owner: ZacHooper
- Created: 2024-06-18T10:08:31.000Z (5 months ago)
- Default Branch: main
- Last Pushed: 2024-06-28T11:44:05.000Z (5 months ago)
- Last Synced: 2024-06-29T01:25:08.889Z (5 months ago)
- Language: Mojo
- Size: 1.3 MB
- Stars: 2
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
- awesome-max-mojo - ZacHooper/mojo-json - json?style=social"/> : Json Parser in Mojo. (Parser)
- awesome-max-mojo - ZacHooper/mojo-json - json?style=social"/> : Json Parser in Mojo. (Parser)
README
# Json Mojo
## Overview
This is a simple JSON parser written in Mojo. It mimics the Python JSON module so you can copy in your existing code and it should work. This is a naive implementation and may not handle all edge cases and may not be the most efficient.
## Usage
```mojo
import json
x = json.loads('{"key": "value"}')
json.dumps(x)
>>> '{"key": "value"}'
```
## Installation
Copy the `json.📦` file into your project and it should be usable.
## TODO
1. ~~Fix parsing of floats.
2. Refactor the parser to use slices of the tokens
3. ~~Checking if the first token is a right brace twice. Should be able to do this once.
4. Add streaming capabilities.
5. ~~Better handle escaped characters in Strings.
6. Moooore performance
7. Add GitHub action to build package
### Edge Cases to Consider
#### 1. Trailing Comma
```json
{
"key1": "value1",
"key2": "value2",
}
```
Trailing commas after the last key-value pair are not allowed in JSON.
#### 2. Missing Quotes around Keys
```json
{
key1: "value1",
"key2": "value2"
}
```
Keys must always be strings enclosed in double quotes.
#### 3. Single Quotes Instead of Double Quotes
```json
{
'key1': 'value1',
"key2": "value2"
}
```
JSON requires double quotes around strings, not single quotes.
#### 4. Non-string Key
```json
{
123: "value"
}
```
Keys must be strings enclosed in double quotes.
#### 5. Invalid Unicode Characters
```json
{
"key": "value\uZZZZ"
}
```
`\u` must be followed by four hexadecimal digits.
#### 6. Unescaped Control Characters
```json
{
"key": "value\u0001"
}
```
Control characters must be properly escaped.
#### 7. Dangling Quotes
```json
{
"key": "value"
"key2": "value2"
}
```
Missing commas between key-value pairs.
#### 8. Special Numbers
```json
{
"number": NaN
}
```
`NaN`, `Infinity`, and `-Infinity` are not valid values in JSON.
#### 9. Nested Structures
```json
{
"nested": {
"nested2": {
"nested3": {
"nested4": {
"nested5": "value"
}
}
}
}
}
```
Extreme nesting could potentially break a parser if recursion depth is not handled properly.
#### 10. Mixed Array Types
```json
{
"array": [1, "string", true, null, {"key": "value"}, [1, 2, 3]]
}
```
While this is valid JSON, it could cause issues in parsers that expect arrays to be homogenous.
#### 11. Big Numbers
```json
{
"bigNumber": 1234567890123456789012345678901234567890
}
```
Large numbers can cause precision loss issues in parsers that don't handle them correctly.
#### 12. Circular References (though not valid JSON)
```json
{
"key": "value",
"self": { "$ref": "$" }
}
```
Circular references are not valid in JSON but if your parser encounters them, it could fail unless special handling is implemented.
#### 13. Duplicate Keys
```json
{
"key": "value1",
"key": "value2"
}
```
JSON doesn’t technically disallow duplicate keys, but parsers should decide how to handle them (`value2` will overwrite `value1` in most parsers).
## Progress
V0.0.1
- Working but slooooow. So long that I didn't wait to see when it finished parsing the canada.json file.
V0.0.2
- Addressed copy issues.
- Now parses the canada.json file in 700ms on my hardware. Still slow but actually usable now.