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.

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

Very parse, no json. Sad shibe. #4

Open
Akii opened this issue Jun 9, 2014 · 3 comments
Open

Very parse, no json. Sad shibe. #4

Akii opened this issue Jun 9, 2014 · 3 comments

Comments

@Akii
Copy link

Akii commented Jun 9, 2014

Input DSON: such "foo" is "bar" wow
Output JSON: { foo: 'bar' }

but should be: {"foo": "bar"}

No parse :(

PS: Nice job though :)

@remixz
Copy link
Member

remixz commented Jun 9, 2014

Ah, yeah, I suppose that's true. I modeled DSON.parse after JSON.parse, which parses JSON into a JS object. The best solution might be to JSON.stringify the object that DSON.parse returns.

@Akii
Copy link
Author

Akii commented Jun 10, 2014

Indeed, that seems to fix it. Is that something DSON.parse should do?

@Akii
Copy link
Author

Akii commented Jun 10, 2014

Speaking of parsing, I've found another "issue" it seems.

Parsing this https://github.com/Akii/Fleapack.Shiba.Doge/blob/master/Configuration/Settings.dson with DSON.djs results in following JSON (after putting it through JSON.stringify):

{
  "Fleapack": {
    "Shiba": {
      "Doge": {
        "dogeifyModes": "0.9"
      }
    }
  }
}

According to the specification the modes should be an array.. and so on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants