Skip to content
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

Improve the usability of HTTP API documentation #1321

Open
7 tasks
KrishnaIyer opened this issue Apr 17, 2024 · 0 comments
Open
7 tasks

Improve the usability of HTTP API documentation #1321

KrishnaIyer opened this issue Apr 17, 2024 · 0 comments
Assignees
Milestone

Comments

@KrishnaIyer
Copy link
Contributor

Summary

Improve the usability of HTTP API documentation

Why do we need this ?

Based on feedback on talking to customers, there are concrete updates that we can do.

What is already there? What do you see now?

Our first version of the API docs: https://www.thethingsindustries.com/docs/api/reference/http/

What is missing? What do you want to see?

Improved usability

How do you propose to document this?

  • Split the APIs into different files. openapi.html should accept a service tag as a parameter and only create the relevant services.
  • Improve the request sections by indicating which params are path, query and body.
  • For body params,
    • Link directly to the message instead of the unfolded JSON schema. When users click and go to the message, add an option for users to select fields in a message to generate a JSON.
    • For body params with field masks, implement the above directly in the request location. Allow users to choose the fieldmasks and then generate a JSON for that fieldmask.
  • (Optional): Allow users to try requests using input fields
  • (Optional): Add a global "server" component that can be set by the user and is applied across the entire documentation.

Can you do this yourself and submit a Pull Request?

Yes

@KrishnaIyer KrishnaIyer added this to the Apr 2024 milestone Apr 17, 2024
@KrishnaIyer KrishnaIyer self-assigned this Apr 17, 2024
@github-actions github-actions bot added the needs/triage We still need to triage this label Apr 17, 2024
@KrishnaIyer KrishnaIyer removed the needs/triage We still need to triage this label Apr 18, 2024
@KrishnaIyer KrishnaIyer modified the milestones: Apr 2024, May 2024 May 2, 2024
@KrishnaIyer KrishnaIyer modified the milestones: May 2024, Jun 2024 May 16, 2024
@KrishnaIyer KrishnaIyer modified the milestones: Jun 2024, Sep 2024 Jul 1, 2024
@KrishnaIyer KrishnaIyer modified the milestones: Sep 2024, Oct 2024 Aug 29, 2024
@KrishnaIyer KrishnaIyer modified the milestones: Oct 2024, Pipeline Oct 10, 2024
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