Skip to content

API documentation inconsistencies #9637

Open
@ederuiter

Description

@ederuiter

Description

When working with the API I came across a number of documentation inconsistencies:

  • all API calls for users refer to {username} .. however looking at the fields of a user there is no username field, only login. More confusingly creating a new user does list the username field but it also lists the login_name field but not the login field

  • all API calls for repos refer to {owner} .. a repository does have an owner, but in this case the {owner} can also refer to an org, so maybe we should refer to this as {parent} .. but the api documentation for the Models lists the parent field, but not its type.

  • all API calls for repos refer to {repo} .. is this the name or the id? This is not clear from the docs

  • I was going to mention that the responses/body are only represented by example values .. but it turns out you can click on "model" to get the definition .. this is nice, but not very obvious from the UI (I only found out when writing this issue).

None of these issues are showstoppers for working with the API .. but it increases the number of wtf's per minute greatly when first working with the API

Metadata

Metadata

Assignees

No one assigned

    Labels

    issue/confirmedIssue has been reviewed and confirmed to be present or accepted to be implementedtype/docsThis PR mainly updates/creates documentation

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions