Skip to content

Expand forge aliases when requirement is parsed #1385

New issue

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

Merged
merged 10 commits into from
Apr 29, 2025

Conversation

ire4ever1190
Copy link
Contributor

Fixes #1341

This moves the expansion step to when the requirement is parsed (meaning a PkgTuple now again only refers to a URL or a package). This removes the need to have special handling for the SAT solver/lock files.

…s either a URL or a package)

Means we aren't having to expand it all over the place
Make the test look like other tests
Since it doesn't exist locally I can't use the vcs check function. I don't need it all anyways so easier to copy a minimal version once than to add another random flag parameter
Issue was it was checking the binary exists without adding the binary extension
@ire4ever1190
Copy link
Contributor Author

Don't know why the CI isn't running again, but passed in my repo

@jmgomez
Copy link
Collaborator

jmgomez commented Apr 28, 2025

Don't know why the CI isn't running again, but passed in my repo

Not sure why CI didnt get triggered. Try closing it and reopen

@ire4ever1190
Copy link
Contributor Author

Don't know why the CI isn't running again, but passed in my repo

Not sure why CI didnt get triggered. Try closing it and reopen

Age old trick of turning it off and on again works =P
Thanks

@jmgomez jmgomez merged commit d564b2f into nim-lang:master Apr 29, 2025
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Dependecies that use forge aliases do not appear in lock file
3 participants