Skip to content

Fix long running tests in support of migration to esbuild#1081

Draft
MicroFish91 wants to merge 21 commits into
mainfrom
mwf/inc-lime
Draft

Fix long running tests in support of migration to esbuild#1081
MicroFish91 wants to merge 21 commits into
mainfrom
mwf/inc-lime

Conversation

@MicroFish91
Copy link
Copy Markdown
Contributor

@MicroFish91 MicroFish91 commented May 19, 2026

Tests are now updated to be compatible with the ES build work. I also fixed a few smaller issues that cropped up since the tests hadn’t been running for a while.

One annoying change: I used to just delete the .vscode/ folder in each project between deployments and that worked just fine... but that’s apparently no longer enough. I assume a newer VS Code update introduced some kind of caching behavior that now has to be explicitly reset through the API; otherwise deployments can still pick up older cached settings even if the folder was deleted.

Update: The remote subscription we use only seems to support 1 container environment so I'm requesting an increase in quotas before I do a final verification pass

@MicroFish91 MicroFish91 changed the title Fix long running tests in support of migration to ES build Fix long running tests in support of migration to esbuild May 19, 2026
Comment thread .vscode/settings.json
".vscode-test": true
}
},
"js/ts.tsdk.path": "node_modules/typescript/lib",
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Fixes the mocha warnings that have been showing up

Comment thread .vscode/launch.json Outdated
return {
name: localize('containerAppEnvironment', 'Container Apps Environment'),
value: nonNullValueAndProp(context.managedEnvironment, 'name'),
value: context.managedEnvironment?.name ?? context.newManagedEnvironmentName ?? '',
Copy link
Copy Markdown
Contributor Author

@MicroFish91 MicroFish91 May 19, 2026

Choose a reason for hiding this comment

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

Note for future confirmations - we should prefer optionals over nonNull for these sections, I think it can still run when users select to create a new resource, in which case it could still be undefined when this gets run

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant