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

feat(synthetics): Added deprecation notes #7224

Merged
merged 1 commit into from
Apr 21, 2022
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,10 @@ If you're using an older monitor version, see the [monitor version 0.5.0 and 0.6

For more on monitor versions and runtime differences, see [Runtime environments](/docs/synthetics/new-relic-synthetics/scripting-monitors/scripted-monitor-runtime-environment).

<Callout variant="important">
Selenium WebDriver promise manager / control flow allowed some functions to execute in order, without manually managing promises/async functions. This was removed in Selenium WebDriver 4.0 and is no longer available in the runtime. All async functions and promises need to be managed with `await` or with `.then` promise chains. This will ensure script functions execute in the expected order.
</Callout>

## Top-level functions: Build your script [#structure]

New Relic calls top-level functions directly from your `$webDriver` instance. These provide a wide range of functionality that covers many basic scriptable actions.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -68,16 +68,16 @@ The new synthetic monitoring runtime includes out-of-the-box timing details when

## Deprecated features [#deprecated]

We’re introducing new language that changes the [script syntax](/docs/synthetics/synthetic-monitoring/scripting-monitors/synthetic-scripted-browser-reference-monitor-versions-chrome-100) in your scripted browser monitors. The new runtime is backwards compatible with legacy runtime syntax. To avoid breaking monitors during the upgrade process, you may receive a deprecation warning in your script log output.
The new runtime includes syntax changes and other deprecations. We’re introducing new language that changes the [script syntax](/docs/synthetics/synthetic-monitoring/scripting-monitors/synthetic-scripted-browser-reference-monitor-versions-chrome-100) in your scripted browser monitors. The new runtime is backwards compatible with legacy runtime syntax in most cases. To avoid breaking monitors during the upgrade process, you may receive a deprecation warning in your script log output.

<table>
<thead>
<tr>
<th style={{ width: "100px" }}>
Deprecated syntax
Deprecated
</th>
<th>
New syntax
New (if applicable)
</th>
<th>
Why?
Expand Down Expand Up @@ -119,5 +119,17 @@ We’re introducing new language that changes the [script syntax](/docs/syntheti
New Relic is committed to inclusivity, which you can read more about on our [diversity, equity, and inclusion page](https://newrelic.com/about/diversity-equity-inclusion).
</td>
</tr>

<tr>
<td>
Selenium WebDriver promise manager / control flow
</td>
<td>
Use `async/await` or `.then` to handle promises
</td>
<td>
Selenium WebDriver promise manager / control flow allowed some functions to execute in order, without manually managing promises / async functions. This was removed in Selenium WebDriver 4.0 and is not available in the new runtime. All [async functions and promises](/docs/synthetics/synthetic-monitoring/scripting-monitors/synthetic-scripted-browser-reference-monitor-versions-chrome-100) need to be managed with `await` or with `.then` promise chains. This will ensure script functions execute in the expected order.
</td>
</tr>
</tbody>
</table>