05:11 <FromGitter> <galvertez> anybody know how to use `JSON::Builder` to intentionally build invalid json? i have a spec that requires invalid json and nothing i've tried works. would rather prefer to use the builder instead of just an ad-hoc string if possible

05:12 <FromGitter> <galvertez> that feel when `JSON::Builder` is too good and won't let you do a bad

07:34 <FromGitter> <Dan-Do> > https://carc.in/#/r/dfnm something like this i think ⏎ ⏎ it failed with complicate structure https://carc.in/#/r/dfql

12:04 <FromGitter> <Daniel-Worrall> How invalid? Do you have an example

12:50 <FromGitter> <Blacksmoke16> @galvertez https://play.crystal-lang.org/#/r/dfru

12:54 <FromGitter> <Blacksmoke16> the trick is not using the block versions of the methods

15:14 <FromGitter> <moe:busyloop.net> for a spec i would rather embed invalid json as a string

15:15 <FromGitter> <moe:busyloop.net> (easier to understand what's going on for older self or next-maintainer)

18:10 <FromGitter> <galvertez> you might be right about that @moe:busyloop.net

18:10 <FromGitter> <galvertez> just seems wonky because of how much of the API using a string bypasses

18:11 <FromGitter> <galvertez> that being said, if i did just use a straight up string, the aspect in question would still satisfy the spec

18:13 <FromGitter> <galvertez> but the test case is literally `it "handles an rpc call with invalid JSON" do` lol so i just made a helper class w/ a method `invalid_json`

18:15 <FromGitter> <Blacksmoke16> you def can make invalid json with the builder, checkout the playground link

18:16 <FromGitter> <galvertez> ya i saw - that should do everythign i need

18:16 <FromGitter> <galvertez> thank you :D

18:18 <FromGitter> <galvertez> i did something similar, except that i did it inside a class and defined `to_json(builder : JSON::Builder)` and it doesn't like that. i assume because of implicit usage of block versions of the methods

18:18 <FromGitter> <galvertez> when calling `to_json` on the intance

18:19 <FromGitter> <galvertez> (https://files.gitter.im/5588134315522ed4b3e2629f/NlBY/image.png)

18:21 <FromGitter> <galvertez> sorry for a screenshot, but it's from my playground server on my homelab. i think i'm putting too much thought into this either way. i think moe is right. a string should suffice for this particular spec

18:24 <FromGitter> <galvertez> sure do, section 7 "Examples" https://www.jsonrpc.org/specification#examples; 6th example

18:25 <FromGitter> <Blacksmoke16> well i mean in this case its not wrong

18:25 <FromGitter> <Blacksmoke16> just never call `end_object` and call it a day

18:25 <FromGitter> <Blacksmoke16> and will generate like `{"key":"value"` which is still invalid

18:25 <FromGitter> <Blacksmoke16> unless you need it to be a specific form of invalid?

18:26 <FromGitter> <galvertez> well i was hoping to implement https://www.jsonrpc.org/specification#examples exactly as seen, or as close to it as possible

18:27 <FromGitter> <galvertez> doesn't matter if it's 1 char off or 1000, invalid json is invalid json.

18:27 <FromGitter> <galvertez> so whether i `end_array` or just never close the object. it's still invalid

18:27 <FromGitter> <galvertez> good enough for rock'n'roll

18:27 <FromGitter> <Blacksmoke16> yea the builder is somewhat smart to prevent missing `{` and `]`, but shouldn't really matter

18:27 <FromGitter> <Blacksmoke16> if you really wanted could prob just redefine `to_json : String` and return a scalar sting

18:27 <FromGitter> <Blacksmoke16> string

18:33 <FromGitter> <galvertez> ya i actually wound up doing it w/ a plain io after i first posted just to get past it

18:34 <FromGitter> <galvertez> also i gotta say. i just the other day got the playground up and running and i really like it a lot. haven't tried out the interpreter yet but the playground is really cool and does most of what i'd want out of an interpreter