-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Feature Request: Endpoint YAML #2964
Comments
Hi! Thanks for the suggestion. How would this feature be used? |
@paulmelnikow This feature would be used by people who have never used JSON but still want the endpoint badge. |
Are you saying you'd like to be able to deploy a custom endpoint that responds with YAML instead of JSON and have the endpoint badge be able to handle that YAML response? In parallel/in the interim, have you tried using our Dynamic (or Static) YAML badge? |
@calebcartwright Yes, I have tried using the dynamic badge but I couldn't get it to work. |
YAML has advantages as a human-editable format, though as a format for communicating between servers it doesn't, and hence is hardly ever used as one. I'm not yet convinced that endpoint YAML makes anything possible that isn't already possible. I'm open to reconsidering in relation to a specific use case. |
Argumentation: Users, not bots write configuration for endpoints → YAML or TOML would be better than JSON. Thanks. |
I’m still a bit confused, as API endpoints aren’t configuration files. If you have a use case that requires hand-crafting a |
👍 in general, the endpoint badge covers the case when the data needs to be machine-generated. If I wanted to produce the example given in the top post, instead of making a JSON endpoint which returns {
"schemaVersion": 1,
"label": "hello",
"message": "world",
"color": "lightgrey"
} we can just hard-code https://img.shields.io/badge/hello-world-lightgrey.svg |
Feel free to comment if there's new information here. |
📋 Description
I understand that the
Endpoint
badge is still in BETA, but it would be useful for the badge to use YAML as well as JSON.It is just an idea, but I think that it would help some people who use YML more than JSON. Here is a comparison:
JSON
YAML
The text was updated successfully, but these errors were encountered: