-
Notifications
You must be signed in to change notification settings - Fork 4
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
[ci-visibility] Add "ci_visibility"
Property and "ci-test"
Session Type
#49
[ci-visibility] Add "ci_visibility"
Property and "ci-test"
Session Type
#49
Conversation
@@ -180,6 +180,19 @@ | |||
}, | |||
"readOnly": true | |||
}, | |||
"ci_visibility": { |
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 wonder how this section (property) would be used from let's say mobile sdk perspective ? Is this meant to be used on all platforms ?
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 hadn't thought about it, but yeah, I don't see why not, there is no technology leakage. We currently use the trace id for the cypress poc, which could be reused for others
ci_visibility
Propertyci_visibility
Property and 'ci-test' Session Type
@@ -45,7 +45,7 @@ | |||
"type": { | |||
"type": "string", | |||
"description": "Type of the session", | |||
"enum": ["user", "synthetics"], | |||
"enum": ["user", "synthetics", "ci-test"], |
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 about having the same wording for both session type and extra context key?
ci_visibility
VS ci-test
ci_visibility
Property and 'ci-test' Session Type"ci_visibility"
Property and "ci-test"
Session Type
Related PR: DataDog/browser-sdk#1192
ci_visibility
property.'ci-test'