It would be really helpful if a few people could take a run though the track and look for mistakes/improvements/etc. Particularly in the documentation and extra-particularly in the concepts. Feedback here or as a github issue is most welcome.
It’s been great fun to learn the language while creating the track. I’m super excited to share the track, and I’m this close I think.
Clicking on “Your published solution” (https://exercism.org/tracks/jq/exercises/hello-world/solutions/IsaacG) is not showing me the solution. Instead, I just land back on the exercise page (https://exercism.org/tracks/jq/exercises/hello-world).
This might just be a “unreleased track” bug, though.
It also might be a “hello-world” specific quirk: there’s no “Community solutions” tab on the HW Exercise, for any track I think. I get the same thing on the Perl track for instance. @ErikSchierboom is this a bug?
A general thing I’m noticing is that the test output is truncated right before the part I’d
like to see, which is rather unfortunate. I’m not sure if that could be addressed.
That would be nice. The thing is that jq is quite a different language from what people are accustomed to. For instance, ruby’s basics essentially says (to my recollection) “ruby has functions like other languages”. There’s probably some example snippets that can be left out, and the functions & operators can be trimmed.
I finished the syllabus! I found it very well written. The exercises took me a bit more work than I anticipated. For the ingredients exercise, it might be helpful, if possible, to actually leave the json data file there for users to use to try things out. Having it hidden inside the bats file makes it harder to mess around with it.
Having comments with what’s needed next in the editor makes lift simpler.
I got tripped up over lacking the () for |length.
I’ve done this in the past, so it wasn’t a big deal. But it took me a while to realize I needed to access a second list of ingredients. That part confused me.
Definitely.
This is the part that gave me the hardest time. I ended up using toentries | fromentries in my first iteration.
They do indeed address the very points that were confusing.
I had to download the exercise locally to make sense of what was going on, which was fine as long as I used WSL, while i saw there is a native Windows binary for jq, this is likely not recommended for this because the differences for shell quoting in Powershell get incredibly complicated. Making it more accessible in the online editor would be a priority imo.
this close I think.
