feat: support parsing mix.lock
#124
Merged
Conversation
This file contains 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
G-Rath
force-pushed
the
support-parsing-mix
branch
5 times, most recently
from
06f08b9
to
70d0585
Compare
joshmcarthur
approved these changes
Jun 26, 2022
G-Rath
force-pushed
the
support-parsing-mix
branch
2 times, most recently
from
74cd04f
to
9f504f2
Compare
G-Rath
force-pushed
the
support-parsing-mix
branch
from
9f504f2
to
faf4fef
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This adds initial support for parsing
mix.lockfiles - this is not an ecosystem/language/tool (Elixir/Erlang) I'm familiar with so I'm taking a blind approach: everything I've seen so far in my research indicates this is a well formatted and stable file, so I'm parsing it as such.If folks report issues we can expand the parser to support those if/when they come up.