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

Project tree items are not updated with VCS status colors after changes in the terminal #10875

Closed
vinokurig opened this issue Aug 22, 2018 · 1 comment
Assignees
Labels
kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system. sprint/next
Milestone

Comments

@vinokurig
Copy link
Contributor

vinokurig commented Aug 22, 2018

Description

Project explorer shows outdated VCS status colors on its item if changes were done but the project explorer tree was collapsed and the file wasn't opened in the editor.

Reproduction Steps

  1. Create a Git project
  2. Do not open any files. Expand and collapse back the project's directory in the project explorer.
  3. Edit any file from the project's root directory in the terminal e.g. with the help of mcedit.
  4. Expand the project's root directory in the project explorer.
    WRONG: The file is not colored as modified. It will be colored in blue after the page refresh.
    Expected: The file must be colored in blue (edited).

OS and version:
Version: 6.10.0-SNAPSHOT
Diagnostics:

@vinokurig vinokurig added kind/bug Outline of a bug - must adhere to the bug report template. team/ide labels Aug 22, 2018
@bencaldwell
Copy link

It would also be useful if the changes were visible on the project root directory in project explorer e.g:

  1. Collapse project root directory in project explorer
  2. Make changes to project files in terminal
  3. The project name changes color to blue to indicate changed files inside

@vparfonov vparfonov added severity/P2 Has a minor but important impact to the usage or development of the system. sprint/next labels Sep 14, 2018
@vparfonov vparfonov added severity/P1 Has a major impact to usage or development of the system. and removed severity/P2 Has a minor but important impact to the usage or development of the system. labels Oct 17, 2018
@vzhukovs vzhukovs self-assigned this Oct 26, 2018
@vzhukovs vzhukovs added this to the 6.14.0 milestone Nov 8, 2018
@vzhukovs vzhukovs closed this as completed Nov 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system. sprint/next
Projects
None yet
Development

No branches or pull requests

4 participants