-
Notifications
You must be signed in to change notification settings - Fork 267
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
delete.term doesn't always work for dependents results #5083
Comments
Unfortunately, transcript
The results of We can easily delete
We can
but deleting (which expects a
Using the expanded term also fails.
But adding the missing namespace works.
The issue seems to be that the I don’t think this is related to the numbered args changes, because I don’t see anything relevant around where I think this is another face of #1298 – if we had absolute (or hash-qualified) names produced, there would be no confusion/ambiguity when they’re presented to |
Describe and demonstrate the bug
If you run
dependents
and then try todelete.term
with a numbered result it doesn't work (or at least not always).Below you can see that it works if I manually select the fully-qualified name.
Screenshots
Environment (please complete the following information):
ucm --version
335512eAdditional context
It's possible that this is a regression that was introduced at the same time that #5055 was, but I haven't verified that. cc @sellout
The text was updated successfully, but these errors were encountered: