-
-
Notifications
You must be signed in to change notification settings - Fork 78
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
fix for attempting to remove a lib when dev is set #644
Open
ninjamuffin99
wants to merge
5
commits into
HaxeFoundation:development
Choose a base branch
from
FunkinCrew:remove-git-fix
base: development
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 4 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
ebfb98d
fix for attempting to remove a lib when dev is set
ninjamuffin99 ea5a1eb
add extra info to the throw
ninjamuffin99 7773c36
run.n
ninjamuffin99 178ce0c
set to most recent haxelib if we remove our currently used haxelib
ninjamuffin99 d99f937
don't set the new haxelib unless we've already established we're usin…
ninjamuffin99 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Binary file not shown.
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We really don't want that. Especially since you're also doing it when removing a version that is not the current version.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah I was incorrect with this one yes.
The intention was for the case of using a dev version and if you were to remove the current version, it doesn't change anything in the
.current
file.If you're on say
flixel 5.0.0
(cat flixel/.current
->5.0.0
), begin using a dev directory for flixel, do something likehaxelib remove flixel 5.0.0
, we want to properly update.current
so if you disable the dev, it leads to whatever the most recent directory isversions.pop()
.However you're right, my implementation is incorrect since we don't want to remove / set the current version unconditionally!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
how does something like
shake out? Unless I'm still misunderstanding 🙇♂️
In this snippet, the code will run if
.dev
DOES exist (otherwise we would have thrown an error earlier). So if we have a.dev
haxelib, and we just removed our.current
set haxelib, we update the.current
file to the most recent version we have installed. Again, only if we are:haxelib dev
based haxelib