This repository was archived by the owner on Jul 14, 2026. It is now read-only.
Repository navigation
Include special packages in package_names.csv - #127
Merged
Merged
Conversation
The package_names.csv published to hexdocs.pm was generated solely from the Hex registry names, so the Elixir standard library applications and Hex itself (the special packages, which are documented on hexdocs.pm but not published as Hex packages) were absent. Consumers such as the hexdocs search autocomplete therefore could not list them. Prepend the configured special package names so the file reflects the same authoritative set the rest of the producer uses.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The package_names.csv published to hexdocs.pm was generated solely from the Hex registry names, so the Elixir standard library applications and Hex itself (the special packages, which are documented on hexdocs.pm but not published as Hex packages) were absent. Consumers such as the hexdocs search autocomplete therefore could not list them.
Prepend the configured special package names so the file reflects the same authoritative set the rest of the producer uses.