-
Notifications
You must be signed in to change notification settings - Fork 198
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: [dart_cli] Activating a cli project after updating files and version doesn't use the new version #1078
Comments
Thank you for bringing this to our attention @eripoll I was able to reproduce this with the steps and also reproduced it with both the I suspect this is some strange |
Good to hear you were able to reproduce! I was going bonkers here 😀
|
@wolfenrain |
I had some time to look into this and it does seem related. Downgrading to an older version of Dart (and by extension pub) allowed me to install CLIs locally and test changes on them but that is more of a temporary solution than a fix. Seems we just have to wait until the Dart team fixes it for us. |
Moving this to the backlog so we don't keep carrying it across iterations in the Blocked column. We are not going to take action on this until we see some movement on the linked Pub issue as that's the root cause of this issue unfortunately. |
Description
For some reason I can't figure out, for the past three days, no matter how I try to do it, as I am developing my dart_cli template-base CLI project, whenever I change anything in a file and activate the package, the newest version of the file is not the one I see when testing my cli.
Steps To Reproduce
dart pub global activate very_good_cli
to get the latest version of very_good_clivery_good create dart_cli sfdk_cli
to create a brand new CLI projectdart pub get
in the newly created project to get dependencies.dart pub global activate --source path .
to build and install the executable without changing anything in the project.sfdk_cli --version
which is expected.
0.0.2
in thepub spec.yaml
file anddart pub global activate --source path .
againwhich is expected (except for the dependencies issues)
sfdk_cli --version
again0.0.1
If I change anything in the files from the template, like just changing the help text from
Print the current version.
toPrint the current version of the CLI.
, if I add any debugging instructions, NOTHING is being picked, as if the package is stuck to the previous version.Cleaning the cache, deactivating, etc do not change a thing.
I have also been unable to fix the dependency constraints issues...
Additional Context
My dart version is
Dart SDK version: 3.4.3 (stable)
MacOS 14.5 (23F79)
Any thoughts? Can anyone reproduce? I've been going insane for the past couple days trying to figure this out...
The text was updated successfully, but these errors were encountered: