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

[markers] add problem decorator fontData #6863

Merged
merged 1 commit into from
Mar 26, 2020
Merged

Conversation

vince-fugnitto
Copy link
Member

@vince-fugnitto vince-fugnitto commented Jan 10, 2020

Signed-off-by: vince-fugnitto vincent.fugnitto@ericsson.com

What it does

  • added fontData to the problem decorators in the explorer which decorates the node with a foreground color with the highest marker severity.
  • added a new method getPriority() which takes as argument a marker diagnostic and returns it's priority which is used when decorating. Markers with a higher severity have a higher priority.

How to test

  1. start the application with a given workspace
  2. create problem markers
  3. ensure that the explorer view is opened, verify that nodes for the given files with problems are correctly decorated.

Screen Shot 2020-01-10 at 2 41 48 PM

Review checklist

Reminder for reviewers

@vince-fugnitto vince-fugnitto added the markers issues related to problem markers label Jan 10, 2020
@vince-fugnitto vince-fugnitto self-assigned this Jan 10, 2020
Copy link
Member

@paul-marechal paul-marechal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, tree is nicely colored. Wasn't able to try warnings though.

@vince-fugnitto
Copy link
Member Author

vince-fugnitto commented Jan 24, 2020

LGTM, tree is nicely colored. Wasn't able to try warnings though.

@marechal-p
I created a sample extension and workspace for which you can try out warnings :)

Open the diagnostic-marker-sample as a workspace, and include the .vsix :)


Screen Shot 2020-01-24 at 10 08 53 AM Screen Shot 2020-01-24 at 10 09 13 AM

@vince-fugnitto
Copy link
Member Author

@lmcbout would you like to try the pull-request?

Copy link
Contributor

@lmcbout lmcbout left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Works well
Explorer view adjusts the color according to the severity of the error

@akosyakov
Copy link
Member

anything else has to be done before merging?

@vince-fugnitto
Copy link
Member Author

anything else has to be done before merging?

@akosyakov no there shouldn’t be anything else, I was hoping for others to give a review as well but if we are happy with the changes I will merge :)

@vince-fugnitto
Copy link
Member Author

I'll merge the pull-request tomorrow morning if there are no objections.

- added `fontData` to the problem decorators in the explorer which
decorates the node with a foreground color with the highest marker
severity.
- added a new method `getPriority()` which takes as argument
a marker diagnostic and returns it's priority which is used when
decorating. Markers with a higher severity have a higher priority.

Signed-off-by: vince-fugnitto <vincent.fugnitto@ericsson.com>
@vince-fugnitto vince-fugnitto merged commit b0eb8e2 into master Mar 26, 2020
@vince-fugnitto vince-fugnitto deleted the vf/problem-decorator branch March 26, 2020 12:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
markers issues related to problem markers
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants