feat(core/hex): Gleam package support#290
Merged
Merged
Conversation
github-actions
Bot
added
documentation
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What has changed?
Gleam publishes to the same hex.pm registry as Elixir, so this extends the existing Hex adapter to handle
gleam.tomlpackages rather than adding a separate ecosystem. It also hardens the Mix adapter, where a git dependency sharing a name with a workspace member could be mistaken for an internal one.How is it tested?
Unit tests in
hex/gleamandhex/mixcover discovery, dependency linking,gleam.tomlediting, publishability, and lockfile regeneration. Thegleam/mixsubprocess calls are not exercised (no toolchain in CI) as with the other adapters.How is it documented?
The READMEs list Gleam among the supported ecosystems.