ziweiwang
ziweiwang
Hello all, We are now maintaining a fork of this repo as per the request of the Yocto project and this issue is in the work. Please check out this...
Hello all, We are now maintaining a fork of this repo as per the request of the Yocto project and this issue is in the work. Please check out this...
This package is deprecated: https://www.npmjs.com/package/eslint-config-standard-with-typescript
Message not shown in the CI: ``` WARNING: You are currently running a version of TypeScript which is not officially supported by @typescript-eslint/typescript-estree. You may find that it works just...
`.eslintrc.js` format is deprecated as mentioned [here](https://eslint.org/docs/latest/use/configure/configuration-files-deprecated). The new flat config is recommended: https://eslint.org/docs/latest/use/configure/configuration-files The maintainer of the deprecated `eslint-config-standard-with-typescript` (as mentioned [here](https://github.com/yoctoproject/vscode-bitbake/pull/277#issuecomment-2265879272)) recommends this [config](https://www.npmjs.com/package/eslint-config-love) which requires the new...
CI/CD: https://github.com/yoctoproject/vscode-bitbake/actions/runs/11134897021
Our extension can work on vscode `1.75.0` or greater as our [tests](https://github.com/yoctoproject/vscode-bitbake/blob/05299344fc943c6a5e2b15f0ffdab1b241e46ff5/integration-tests/src/runTest.ts#L17) didn't break, we may consider incrementing the version in the `package.json`. > https://github.com/yoctoproject/vscode-bitbake/actions/runs/10205960304/job/28237849507?pr=297#step:15:13
> @WilsonZiweiWang The vscode version should be aligned with the one contained in the client/package.json and server/package.json. Can we edit how the dependency bumps are generated to align all package.json...
> Can this field of ldap not be written dead? The name of the ldap service deployed by oneself may be email @vanche1212 The main purpose of getting this attribute...
> the mail attribute is something the user may have never seen before WebUI will need the email to create the user in the current workflow. Where does that come...