-
Notifications
You must be signed in to change notification settings - Fork 64
General feedback for changelist search and quick pick views #104
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
Comments
Going to edit this with whatever comes to mind, stuff that needs fixing at some point, can collate into issues later or just fix them
|
Fantastic plugin, many thanks for working on it. Do you think it would be feasible to improve the swarm integration? For now I can find a shelf and see a diff, but being able to view and leave new comments would be a great addition. The swarm API seems relatively straightforward, but I don't know the level of complexity that this would pose for the plugin. |
Also very happy with this plugin! I have two things, maybe they already exist but I'm unsure:
|
Hi - thanks for suggestions,
I briefly discussed this in #185 and I think it would be good to be able to select a 'target' changelist for a given scm provider, but also a quite a big job to do it right, covering all the commands and taking account of all the edge cases, which I probably won't get time for any time soon
Yes having a 'reopen' / move changelist command would be a good idea and should be easy to implement (FWIW, within the scm view, the '4 arrows' icon on each file will move between changelists so no right click necessary, and you can multi-select if you have a bunch of files to move at once - but I recognise the slow bit is probably switching between views) |
Would be great for a quick link to show file in remote repo. GitLens has Open File on Remote. |
Uh oh!
There was an error while loading. Please reload this page.
I'm opening this issue to capture general feedback on the changelist search and quick picks. Interested to get a general idea of whether they are useful and whether the interface is intuitive enough / useful enough in real-world scenarios, if you think there's anything missing or anything annoying that gets in the way of being more useful.
Obviously I'm not aiming to fully recreate P4V inside vscode, but I'm hoping that by bringing some more context about file history into the editor it can reduce the amount of time spent switching out to P4V. e.g. to investigate an issue relating to a historic change. There are limitations to what's possible using the vs code API, but little things can make a big difference to how usable it is so any inspiration is helpful.
For reference, these are the views I mean:


If you have a specific bug / enhancement request you can of course also open an issue
The text was updated successfully, but these errors were encountered: