Hey there 👋!

Are you an implementer of a new JSON Schema related tool, or an interested user submitting a tool you like?
If so, thanks for considering adding your tool to our collection -- and if not, sorry, I'm just a bot looking at which pages you're modifying!

Someone will review your pull request shortly.

In the interim, if you haven't already, there's a few things you might be interested in reviewing or confirming:

1. Short description: Tell us a small bit about your tool! We love staying up to date on what's out there, and what your intentions are in writing it.
2. Come Join Our Slack!: We have an #implementers channel for anyone interested in or building JSON Schema tooling!
   An invite can be found here or on our homepage!
3. Common Interfaces: We maintain a page with some "commonly useful programming interfaces" that tooling may want to implement and present to your users.
   You can find that page here in our documentation.
   Have a read through and consider whether you implement or should implement any of what's there.
4. Bowtie Harness: Bowtie is a tool which gives JSON Schema users access to a huge number of different implementations across many languages, and reports on the compliance of those implementations with the JSON Schema specifications.
   If it makes sense for your kind of tool, consider writing a harness which connects it to Bowtie. Instructions for doing so can be found in the tutorial in Bowtie's documentation.

If you have any questions, any feedback, or need help with the submission process, don't hesitate to reach out.
Thanks a bunch for your awesome contribution!

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Need help with finishing up the Tooling Listing Notes because it was way too lengthy as described in #940 . For now, I've selected the shortest of the bullet points mentioned in Tooling Listing Notes in #940 as the placeholder. Please ignore if that gets the job done.

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (33e9315) to head (7eb4464).
Report is 5 commits behind head on main.

@@            Coverage Diff            @@
##              main      #941   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           10        10           
  Lines          373       373           
  Branches        94        94           
=========================================
  Hits           373       373           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@benjagm Please check if the requested changes were made correctly

Hi @benjagm, it seems the only thing pending for the merge to go is for you to approve the changes you requested and already made by @iamAyushChamoli (to add it to util-testing list too)
7eb4464

@benjagm I used this PR for reference and noticed that it didn't include environments which is mentioned as Cypress in the related issue.