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

[dev-tool] Remove stale sample guardrails #24148

Merged

Conversation

witemple-msft
Copy link
Member

This PR removes outdated syntax restrictions from dev-tool when generating samples. This follows the end of our Node.js 12 grace period. Additionally, it increases the compiler target in samples from ES2018 to ES2020.

I've also removed version 12 from the default check-node-versions configuration.

CC @xirzec

@witemple-msft witemple-msft added the dev-tool Issues related to the Azure SDK for JS dev-tool label Dec 6, 2022
@witemple-msft witemple-msft self-assigned this Dec 6, 2022
Copy link
Member

@mpodwysocki mpodwysocki left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@@ -224,7 +224,7 @@ export const commandInfo = makeCommandInfo(
"node-versions": {
kind: "string",
description: "A comma separated list of node versions to use",
default: "12,14,16,17",
default: "14,16,17",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we remove 17 and add 18,19?

@witemple-msft witemple-msft merged commit d707fd8 into Azure:main Dec 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dev-tool Issues related to the Azure SDK for JS dev-tool
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants