Skip to content

Improve Content: Returning response data #63

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

Open
Tracked by #45
AlexanderKaran opened this issue Jan 8, 2025 · 0 comments
Open
Tracked by #45

Improve Content: Returning response data #63

AlexanderKaran opened this issue Jan 8, 2025 · 0 comments
Assignees

Comments

@AlexanderKaran
Copy link
Collaborator

AlexanderKaran commented Jan 8, 2025

The Importance of Naming Things Good

One from the Slack community:

Pradeep: One of my coworkers just posted a sample API response from a vendor that we're integrating with.  Enjoy.

{
    "DataList": [
        {
            "Parameter": 74277,
            "Parameter Label": "TC3 IO; Omni Sensor Setup Program GH1C; OmniSensor Substrate Temperature",
            "DataSet": [
                {
                    "Data": "37.30 °C",
                    "Time": "Tue Aug 24 15:47:47 2021"
                }
            ]
        }
    ]
}

Pradeep  3 days ago
But even more interesting is
37.30 °C is called Data not Temperature
And the value of Tue Aug 24 15:47:47 2021 is being referred to as Time even though it has a date component

One of my pet-peeves when reviewing openapi specs is when people name things badly - or even worse with abbreviations that only they know

Sid Maestre  3 days ago
This should be included in API design books & courses with the prompt ... how would you improve this API response?

@AlexanderKaran AlexanderKaran self-assigned this Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant