We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The JSON data (application/vnd.hex+json) delivered by
is not documented.
While most of the fields delivered can be guessed, some are not obvious. Some examples:
null
Beside a description of the fields, it would be nice to have a specification one can rely on.
(FYI: I'm building a importer from hex.pm packages into guix, for which I need to query this data.)
The text was updated successfully, but these errors were encountered:
See https://github.com/hexpm/specifications/blob/master/apiary.apib#L400 and https://github.com/hexpm/specifications/blob/master/apiary.apib#L471.
Some fields are not documented for every resource because they are following conventions or assume some knowledge about elixir and hex.
You can find information about the package metadata here: https://github.com/hexpm/specifications/blob/master/package_metadata.md.
url
html_url
doc_html_url
inserted_at
updated_at
If you feel anything is missing in the HTTP API docs please send pull requests that fill in the missing information as you learn more. Thank you.
Sorry, something went wrong.
No branches or pull requests
The JSON data (application/vnd.hex+json) delivered by
is not documented.
While most of the fields delivered can be guessed, some are not obvious. Some examples:
null
mean here)Beside a description of the fields, it would be nice to have a specification one can rely on.
(FYI: I'm building a importer from hex.pm packages into guix, for which I need to query this data.)
The text was updated successfully, but these errors were encountered: