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

Update utils #2512

Merged
merged 9 commits into from
Jun 28, 2023
Merged

Update utils #2512

merged 9 commits into from
Jun 28, 2023

Conversation

motm32
Copy link
Contributor

@motm32 motm32 commented Jun 9, 2023

Update needed in order to add support for service connector.

Includes code changes to fix errors that came with updating the package. Also had to update vscode and vscode-azext-dev versions in order to fix all issues.

@motm32 motm32 requested a review from a team as a code owner June 9, 2023 22:47
package.json Outdated
@@ -772,13 +772,13 @@
},
"devDependencies": {
"@microsoft/eslint-config-azuretools": "^0.1.0",
"@microsoft/vscode-azext-dev": "^0.1.3",
"@microsoft/vscode-azext-dev": "^1.0.4",
Copy link
Contributor

Choose a reason for hiding this comment

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

Why not just go directly to 2.0.0 of all these packages?

registerSiteCommand('appService.Redeploy', unwrapArgs(redeployDeployment));
registerSiteCommand('appService.viewDeploymentLogs', unwrapArgs(viewDeploymentLogs));
// eslint-disable-next-line @typescript-eslint/ban-ts-comment
//@ts-ignore
Copy link
Member

Choose a reason for hiding this comment

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

If I recall correctly, I think that what you're ignoring here is fixed by Alex's PR.

Was the ts error related to the arguments not matching the command callback or something?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yup Alex had recommended just ignoring the error with a ts-ignore since I guess he was working on that PR, but I can remove those once the changes are in.

@motm32 motm32 mentioned this pull request Jun 12, 2023
alexweininger
alexweininger previously approved these changes Jun 27, 2023
package.json Show resolved Hide resolved
src/commands/createWebApp/setPostPromptDefaults.ts Outdated Show resolved Hide resolved
@alexweininger
Copy link
Member

Fixup the CI errors and then this is good to go.

@alexweininger
Copy link
Member

Maybe try updating the CI to use Node 16.

Comment on lines 2 to 16
- task: NodeTool@0
displayName: 'Use Node 14.x'
inputs:
versionSpec: 14.x
- task: NodeTool@0
displayName: "Use Node 16.x"
inputs:
versionSpec: 16.x

- task: Npm@1
displayName: 'npm ci'
inputs:
command: ci
- task: Npm@1
displayName: "npm ci"
inputs:
command: ci

- task: Npm@1
displayName: 'Build'
inputs:
command: custom
customCommand: run build
Copy link
Member

Choose a reason for hiding this comment

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

It's really small, but can you revert the inadvertent changes here. Mostly to preserve the git blame for this file.

@motm32 motm32 merged commit 7e3c2bd into main Jun 28, 2023
@motm32 motm32 deleted the meganmott/updateUtils branch June 28, 2023 19:46
@microsoft microsoft locked and limited conversation to collaborators Aug 13, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants