Conversation
Collaborator
|
Thank you @ayushxx01 for your contribution! 🎉 We have merged the Dog API into main via commit �f08258 with schema cleanup (sanitized URL, unlimited rate limit, proper category) and credited you as co-author. Closing this PR as resolved. Welcome to the DevShelf community! 🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
?? Submission Overview
shelf/(e.g.,shelf/cli-tools.json,shelf/apis.json, etc.)?? Validation Checklist
Before submitting, please ensure you have checked the following:
name,url,category,description) are filled out correctly.mainbranch.?? Additional Notes / Context
I have tested the Dog API endpoint 9-10 times using
curl.and API successfully returned HTTP 200 with a valid JSON response.
CORS support was verified through the response headers, which mentioned:
access-control-allow-origin: *.The API is accessible over HTTPS, and no API key, authentication, or payment/card details were required during testing.
The entry follows the existing
shelf/apis.jsonstructure and includes the additional metadata requested in issue #18.