-
-
Notifications
You must be signed in to change notification settings - Fork 468
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
sync
not using flags informations from the lock file
#825
Comments
If it does not remember |
Ok, since I now understood it well and looked at the
But then I wanted to test some more and
I also tried a little bit with |
Potentially related comment #811 (comment) |
sync
configuration option for remembering synced featuressync
not using flags informations from the lock file
I edited a little bit my issue so it now points to the real issue, sorry for that |
Found the issue. It's because the lock options are restored too late. I will fix this. |
Hey!
I saw this #677, that closed this #676, but my issue is with the fact that the autosync does not remember the
--all-features
flag.Is there a specific reason for this? When developping a package with extra features, and you want to add a new dependency doingrye add package
,rye
will sync and remove the optional dependencies, so you have to dorye sync --all-features
again, for example.My suggestion would be to have some sort of configuration option to configure sync flags, ideally a per-project option, where I can put something like this:Actually I misread the content from the mentioned PR, but this issue still stands for the fact the
sync
command is not using the flags from the previoussync
stored in the lock file.Thanks for the tool, btw :)
EDIT
Apparently you can have a workaround using what is discussed in #818 by doing
but #818 (comment) says it works more or less by accident and that is why it is not documented, but maybe it would be good to have a nicer way to do it?
The text was updated successfully, but these errors were encountered: