-
Notifications
You must be signed in to change notification settings - Fork 620
Only discard the files changes inside the lane #4820
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
Conversation
When using the file context menu inside a given lane to discard the changes, only the changes to that file inside the lane should be discarded. Any other changes to that same file that live in other lanes are kept
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
8f6330d
to
394f1d9
Compare
claims: filtered_ownership_claims, | ||
} | ||
}) | ||
.context("failed to determin ownership to unapply")?; |
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.
typo!
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.
Oops!
Fixed :)
394f1d9
to
b3c96ab
Compare
It also tries to use `Vec<PathBuf>` in the tauri interface, which is still to be validated.
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.
Thanks so much for all your recent work here (making missing projects deletable was great!).
I took the liberty to edit the rust-side of things so that it's idiomatic and less wasteful. However, I also tried something new which is to pass Vec<PathBuf>
from the frontend to the backend directly. In the frontend, this means that a string-array should be passed and I think it should convert to Vec<PathBuf>
automatically. However, I didn't try it as I didn't adjust the frontend code.
It would be great if it could work like this, but if not, Vec<String>
will be fine, and a conversion to Vec<PathBuf>
in the backend.
Thanks again!
Hey @Byron! Your improvements are more than welcome haha. Thanks! |
I added an e2e testing label here as a reminder this might be a good thing to cover. |
186a8c4
to
c93db0e
Compare
c93db0e
to
50c75ee
Compare
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.
LGTM 🥳
Problem
When using the file context menu inside a given lane to discard the changes, all changes to that file across all lanes are discarded.
This is either weird or unexpected behavior.
Solution
Only discard the changes inside the lane that the context menu was opened from.
Issues
This fixes issue #4137