-
-
Notifications
You must be signed in to change notification settings - Fork 90
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
feat: Added Branches tree view #729
Conversation
Sorry to be a pain but can you get it to refresh when changes are detected like the repo log does. https://github.com/JohnstonCode/svn-scm/blob/master/src/historyView/repoLogProvider.ts#L122 |
the one feature i think maybe should be added before this is merged is a refresh button. do you agree? are there any other features that you think should be added? |
Yes a refresh button would be useful. Apart from that i can think of anything else. |
Not sure if I did this right...I don't know how to trigger the repo change event. |
Yeah seems there is a loop. Let me have a look |
the refresh in |
that's why i put in the "fire" boolean - before it was triggering refresh, then triggering getChildren, etc. i don't think there's an infinite loop anymore - i just don't see the event being triggered at all when i set a breakpoint |
Yeah sorry, the |
Got it |
hmmm...any suggestions? |
Yeah give me a couple of minutes i will give you a patch |
yeah, otherwise the repo may not be on the revision that was just committed (not sure why this is) |
The information from svn info is taken directly from the .svn/entries file, and not from the server. This stems from Subversion's basic design of not requesting information from the repository server whenever possible. |
so maybe i need to do svn info on the URL instead of on the WC? |
That would work. Also you need to add |
Actually it wont be because of the update... |
The manual refresh button might do for the time being. This is a complicated problem |
Correct that it is just using the last revision on master and the new branch commit revision on the branch |
it is working just not updating on future commits |
yeah, i'm seeing that too.. not sure why that's happening since i'm getting the info from the URL |
so to fix it i need to do |
i just need to stop relying on the cache |
also passing the url wasn't working |
should work now |
Yes does appear to be working. Will have a proper look at it tomorrow. Rally good job though. |
thanks! |
oh, i think it's not working entirely for me since there's no .svn in the current folder. i need to modify the watcher to look at a parent path (if that's even possible) |
I guess i'll just have to deal with manually reloading since my directories are often laid out so the .svn directory is in a higher level directory |
I made some changes to use |
It only works on Windows and Mac and is unneeded since wc.db is in the .svn directory
Yeah seems to be working. |
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
# [2.1.0](v2.0.2...v2.1.0) (2019-11-13) ### Features * Added Branches tree view ([#729](#729)) ([cecd185](cecd185))
🎉 This PR is included in version 2.1.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Woohoo! Thanks! |
this adds a new tree view that gives you a nice listing of all the files that changed between the current branch and the branch it was copied from.
tooltip:
clicking something marked M will open up a diff: