Julian Berman

Apologies for not getting much time to think about this myself yet (and therefore not responding) -- I appreciate your thoughts and definitely your offer to look into this! As...

Hey! Yeah I'd certainly accept a PR to add it, I just hadn't had a need for it at the time I wrote most of these bindings so I didn't...

Likely less useful if done in that way, though even if you only know Python, a useful contribution would be extending the test suite to cover it, that's the first...

Hi thanks for raising and apologies that my reply will be both late and short. Do feel free to prod again though. (I sympathize, as you're not the first person...

This seems reasonable though a better design is probably to allow for format strings, e.g. `filter-dialects --format {.short_name}: {.pretty_name}` rather than as you say needing to add lots of different...

I'm not sure how much effort it's worth when the even better solution I think is moving implementations to their own separate repo (one per implementation harness) which anyways is...

It's basically supporting every version of an implementation rather than just its latest! We don't yet support it for all implementations (it requires building images and making the harness work...

And I don't have things clearly written out unfortunately mostly because step 0 is "figure out what if anything needs to change to support implementation repositories living in a separate...

This probably slightly complicates the [pre-commit hook ensuring all implementations appear in the file](https://github.com/bowtie-json-schema/bowtie/blob/main/.pre-commit-hooks/check-dependabot). Which is to say -- I'm fine with reviewing a PR to use that syntax of...

Possibly, though note for example we don't currently have any Swift implementations, but if one were added, the point of the check is to remind the author of that PR...