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

fix-9205: Fill task options explicitly if problemMatchers set #10166

Merged
merged 1 commit into from
Oct 18, 2021

Conversation

kostmetallist
Copy link
Contributor

@kostmetallist kostmetallist commented Sep 24, 2021

What it does

Fixes issue 9205. Was originally proposed in #9207 by @vnfedotov. This one resolves conflicts with the stale changes.

How to test

Please see #9207 (comment)

Review checklist

Reminder for reviewers

Signed-off-by: Konstantin Kukushkin [email protected]

Copy link
Member

@msujew msujew left a comment

Choose a reason for hiding this comment

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

Hi @kostmetallist, thank you for your first contribution.

Please be sure to properly sign the eclipse contributor agreement (eca) with the same email as your authorship so we can accept your changes.

@msujew msujew added tasks issues related to the task system vscode issues related to VSCode compatibility labels Sep 24, 2021
@RomanNikitenko
Copy link
Contributor

as far as I understand the changes are taken from #9207
I believe it's better to save authorship...

@kostmetallist
Copy link
Contributor Author

@msujew @RomanNikitenko thanks for the feedback! I've signed the commit and also have provided a reference to author of the original solution from #9207.

@kostmetallist kostmetallist requested a review from msujew October 1, 2021 16:12
@kostmetallist
Copy link
Contributor Author

Hey guys, congrats for the great 1.18 release!

Is there still anything required for the changes to be approved?

@RomanNikitenko
Copy link
Contributor

@kostmetallist
Hello!
Thank you for resolving conflicts!

About

as far as I understand the changes are taken from #9207
I believe it's better to save authorship...

I meant something like that:

Screenshot 2021-10-04 at 10 23 24

Signed-off-by: Konstantin Kukushkin <[email protected]>
Co-authored-by: Vladimir Fedotov <[email protected]>
Originally-proposed-by: Vladimir Fedotov <[email protected]>
@kostmetallist
Copy link
Contributor Author

Hi @RomanNikitenko, I've updated the co-authors for the commit, can you please take a look?

Copy link
Contributor

@RomanNikitenko RomanNikitenko left a comment

Choose a reason for hiding this comment

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

How to test
Please see #9207 (comment)

@kostmetallist
What extension/plugin did you use for testing?

I tried to test according to #9207 (comment) and faced with the problem:

Screen.Recording.2021-10-07.at.13.15.36.mov

@kostmetallist
Copy link
Contributor Author

Thanks @RomanNikitenko for pointing out the issue! I've initialized new testing stand: https://github.com/kostmetallist/theia-problem-matcher-stand. Please make sure to run yarn to install all the required dependencies. Then it is supposed to be run as a plugin.

Attaching GIF showing everything's fine with problem matchers (please note I'm running modified Theia including changes proposed in this PR).

theia-problem-matchers-fixed

Copy link
Contributor

@RomanNikitenko RomanNikitenko left a comment

Choose a reason for hiding this comment

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

Tested according to #9207 (comment) - it works well!
Also tried the changes for typescript and shell tasks - I don't see any regressions!

@kostmetallist
Copy link
Contributor Author

Thanks Roman! How likely the changes are to be included in the upcoming 10/28/2021 release?

@msujew
Copy link
Member

msujew commented Oct 14, 2021

How likely the changes are to be included in the upcoming 10/28/2021 release?

We often times leave PRs open for a few days after approving - assuming there's no urgent reason for merging it - for other reviewers to give their "veto" (i.e. other small issues they would like to see resolved). I'm quite sure that your changes will be included in the next release 👍

@RomanNikitenko You can merge this (as you are the main reviewer) as you see fit. Like we discussed on the recent dev meeting, we try to merge approved PRs in a more timely manner now.

@RomanNikitenko
Copy link
Contributor

RomanNikitenko commented Oct 18, 2021

Sorry for the delay - I had a short vacation, merging the PR...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tasks issues related to the task system vscode issues related to VSCode compatibility
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants