Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Introduce proper custom execution lifecycle #9559
Introduce proper custom execution lifecycle #9559
Changes from all commits
f818296
f78bdeb
3d46c7e
606725c
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
I see that you use
executionId
field to check if it'sCustomExecution
task.So - if only tasks with
CustomExecution
have this field - should we provide some clear/more readable way for that...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.
What do you have in mind? I'm not trying to do any typing here.
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.
is it true?
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.
As far as I know a task of any type (not only
customExecution
) can haveexecution
- the object is created when a task is started ($onDidStartTask() => getTaskExecution()) and is stored to the map with executions usingexecutionId
.I see that:
executionId
field was added to theTaskDto
interfacecustomExecution
first, you create the field, like:
and in the line 281 above you check - if the field exists - then
result.task.execution = this.getCustomExecution(execution.task.executionId);
)So, in my comment above I meant that for me it's not obvious that
executionId
field of theTaskDto
interface is a marker forcustomExecution
tasks.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.
If you think the executionId field is named confusingly, I'm all up for renaming it to something more clear. But since it wasn't introduced in this PR, it's not a concern for this PR.
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.
sorry, but for me it looks like within current PR you are trying to use
common
for all tasks field as a marker forcustomExecution
task. My first comment here was aboutif (execution.task.executionId)
.If I'm not mistaken, this field was introduced within one of your previous PR. If so, it's important to know what you think about it, what intention was...