已关闭
optimize performance by only strict checking for ets file, tsc and linter DFX dotting, buildEnd only memory mode to gc #750
liyancheng创建于 2月26日关闭于 2月27日
openharmony_ci
2月26日 评论：
2月26日 评论：
感谢提交Issue！关于Issue的交互操作，请访问OpenHarmony社区支持命令清单。如果有问题，请联系 [@xucheng46](https://gitcode.com/xucheng46) [@zhuoli](https://gitcode.com/zhuoli) 。如果需要调整订阅PR、Issue的变更状态，请访问链接。
Thanks for submitting the issue. For more commands, please visit OpenHarmony Command List. If you have any questions, please refer to committer gitcode for help. If you need to change the subscription of a Pull Request or Issue, please visit the link.
2月26日 添加了label：waiting_for_assign
Lliyancheng
2月26日 关联了pull request：optimize performance by only strict checking for ets file, tsc and linter DFX dotting, buildEnd only memory mode to gc
2月26日 关联了pull request：optimize performance by only strict checking for ets file, tsc and linter DFX dotting, buildEnd only memory mode to gc
Lliyancheng
2月26日 关联了pull request：optimize performance by only strict checking for ets file, tsc and linter DFX dotting, buildEnd only memory mode to gc
2月26日 关联了pull request：optimize performance by only strict checking for ets file, tsc and linter DFX dotting, buildEnd only memory mode to gc
2月27日 关闭了 issue
Bug Report
🔎 Search Terms
🕗 Version & Regression Information
⏯ Playground Link
Playground link with relevant code
💻 Code
// We can quickly address your report if: // - The code sample is short. Nearly all TypeScript bugs can be demonstrated in 20-30 lines of code! // - It doesn't use external libraries. These are often issues with the type definitions rather than TypeScript bugs. // - The incorrectness of the behavior is readily apparent from reading the sample. // Reports are slower to investigate if: // - We have to pare too much extraneous code. // - We have to clone a large repo and validate that the problem isn't elsewhere. // - The sample is confusing or doesn't clearly demonstrate what's wrong.🙁 Actual behavior
🙂 Expected behavior