The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: Anuj-Rathore24 <[email protected]>
Co-authored-by: t-hamano <[email protected]>
Co-authored-by: shail-mehta <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @Anuj-Rathore24! In case you missed it, we'd love to have you join us in our Slack community.

If you want to learn more about WordPress development in general, check out the Core Handbook full of helpful information.

hi @t-hamano, Thank you reviewing my PR🙇

Both URLs display the same content, with https://json-schema.org/tools being the main page and https://json-schema.org/implementations#editor just linking directly to the relevant section.

I can update the PR to use https://json-schema.org/tools if that’s preferred for consistency with the site's structure. Let me know how you'd like me to proceed!

https://json-schema.org/implementations#editor just linking directly to the relevant section.

This link is redirected to the following link and the #editor seems to be deleted:

https://json-schema.org/tools?query=&sortBy=name&sortOrder=ascending&groupBy=toolingTypes&licenses=&languages=&drafts=&toolingTypes=&environments=&showObsolete=false

I feel https://json-schema.org/tools is the simplest and best.

Thanks for the clarification! 😊

I have updated my PR!!