-
-
Notifications
You must be signed in to change notification settings - Fork 229
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add justinrainbow/json-schema to tooling page #987
add justinrainbow/json-schema to tooling page #987
Conversation
Hey there 👋! Are you an implementer of a new JSON Schema related tool, or an interested user submitting a tool you like? 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:
If you have any questions, any feedback, or need help with the submission process, don't hesitate to reach out. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Welcome to the JSON Schema Community. Thanks a lot for creating your first pull request!! 🎉🎉 We are so excited you are here! We hope this is only the first of many! For more details check out README.md file.
built with Refined Cloudflare Pages Action⚡ Cloudflare Pages Deployment
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
benjagm I am unsure about language versioning in environments
, shouldn't this be in toolingListingNotes
instead? Also, I believe logos should not be dynamic and be hosted as part of the website.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #987 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 10 10
Lines 373 373
Branches 94 94
=========================================
Hits 373 373 ☔ View full report in Codecov by Sentry. |
I have added the image. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot for your help!!
Can you please take a look to my comment?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks Good 🚀
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great! Thanks a lot for this PR.
Congratulations, @heysujal for your first pull request merge in this repository! 🎉🎉. Thanks for your contribution to JSON Schema! |
What kind of change does this PR introduce?
This PR adds
justinrainbow/json-schema
to the tooling page as a validator.As in the mentioned issue, the link for the logo was given. The image is not loading because the URL is not being picked up as it but it is being appended to some directory. Something like below
http://localhost:3000/img/tools/logos/https:/avatars.githubusercontent.com/u/170307068?s=200&v=4
I think this can be fixed by making changes to
next.config.js
This is another issue on its own and I would like to work on it too.
Issue Number:
Screenshots/videos:
![image](https://private-user-images.githubusercontent.com/55016909/372572171-878c5987-cb11-4869-8f02-1b1ddce5f77b.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzg4NzkyNDYsIm5iZiI6MTczODg3ODk0NiwicGF0aCI6Ii81NTAxNjkwOS8zNzI1NzIxNzEtODc4YzU5ODctY2IxMS00ODY5LThmMDItMWIxZGRjZTVmNzdiLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMDYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjA2VDIxNTU0NlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTRkNmFmOGYyZGJlZDU1NzIzMDIzMTQzZjYzNzUwZGEwMjE5MjViNGMyYjRhYTI4YzAxZDIyZGMxMGFiZjNlNTMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.yNjQIg0mvc545LwlN9OeYTEO3VAg156pCLbuSFfKSuk)
If relevant, did you update the documentation?
No
Summary
Does this PR introduce a breaking change?
No