Skip to content
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

Review temp files hangs there after the fact #23

Closed
EthraZa opened this issue Jan 14, 2016 · 5 comments
Closed

Review temp files hangs there after the fact #23

EthraZa opened this issue Jan 14, 2016 · 5 comments
Milestone

Comments

@EthraZa
Copy link

EthraZa commented Jan 14, 2016

When we call to Review pending transfers, a file called sync-summary.json shows up on the editor and on the Working Files.
After we call Commit or close the file (since we don't have the Cancel operation here), the file just hangs there in the Working Files. At any time if we save this file it will be created in the root of the project.

I suggest to delete this file after Commit and to implement a Cancel to delete it before commit as well. Just to get rid with it and keep my Working Files clean. :)

@lukasz-wronski
Copy link
Owner

Maybe I will check if someone try to save it. On save I will show message that this file should not be saved as it's just a temporary thing and won't save it at all? I don't like user to have to cancel the review implicitly.

@lukasz-wronski lukasz-wronski added this to the v0.2.x milestone Jan 14, 2016
@EthraZa
Copy link
Author

EthraZa commented Jan 14, 2016

It is a two parts problem.

1- Discard the file after Commit.
I guess this one is esier. You just need to remove the file on Commit.

2- What to do when we do not want to Commit anymore.
If I right click the json file and delete it, it will ask me if I'm sure and delete, problem resolved.
I just thought that have a Cancel operation to delete the file without confirmation (if possible), would be an alternative. But a not extremely necessary one, since we can already manually delete the file.
Another alternative could be a timeout to delete the file. If you don't commit, or request a new operation, after X seconds the file is gone.

@lukasz-wronski
Copy link
Owner

The file is already discarded after commit, isn't it?
As for the option two - I do not like to add additional command just for that, timeout is not a good option too as someone might like to take it's time on reviewing the file.

I'd like to protect this file from being saved to disk, but right now I can't find suitable vs code api event to do it.

@EthraZa
Copy link
Author

EthraZa commented Jan 15, 2016

No the file does not get discarded after commit. It hangs there and I can redo the Commit how many times I want that it will perform the action.

@lukasz-wronski
Copy link
Owner

This should now close file after a commit. Wait for 0.2.9 to check it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants