-
Notifications
You must be signed in to change notification settings - Fork 63
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
Added support for pm.execution.location
#950
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## develop #950 +/- ##
===========================================
+ Coverage 60.64% 60.71% +0.07%
===========================================
Files 12 12
Lines 559 560 +1
Branches 135 136 +1
===========================================
+ Hits 339 340 +1
Misses 220 220
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
f953d52
to
e012295
Compare
@vedkribhu Need to update the |
3d79620
to
fbf5a14
Compare
f44e700
to
4f5af39
Compare
5f5197e
to
9b9c4aa
Compare
9b9c4aa
to
27aea80
Compare
27aea80
to
f962496
Compare
* @type {ExecutionLocation} - current execution path | ||
* @instance | ||
*/ | ||
location: _assignDefinedReadonly(execution.legacy._itemPath || [], /** @lends ExecutionLocation */ { |
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.
execution.legacy
is not the best way to accept this context. Need to expose a better interface for consumers to pass down all this information.
aad1b76
to
60560f3
Compare
pm.execution.location
pm.execution.location
pm.execution.location
No description provided.