Expose execution context details in hook #32
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vmatyus
force-pushed
the
add-execution-info
branch
2 times, most recently
from
bf1820c
to
849528a
Compare
added 3 commits
February 8, 2022 17:25
Signed-off-by: Veronika Matyus <veronika.matyus@ibm.com>
Signed-off-by: Veronika Matyus <veronika.matyus@ibm.com>
Signed-off-by: Veronika Matyus <veronika.matyus@ibm.com>
vmatyus
force-pushed
the
add-execution-info
branch
from
849528a
to
45b05c2
Compare
|
Our project would need this extension, so I would like to request your review. |
sriv
approved these changes
Feb 15, 2022
|
Done, sorry about the delay. gauge-go 0.3.0 is released and is available in the releases page. Thank you for the changes @vmatyusGitHub ! |
|
@sriv thank you for reviewing! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Relates to #5
In commit: ce4571d you can see a possible solution for this problem.
The changed
func()also could befunc(interface{})instead specific type*m.ExecutionInfolike in case ofStepstruct.