Removing the singletons will help in focusing only on cases which are part of some cluster.

In order to move quickly and release stuff as fast as possible, we decided not to spend too much time writing tests. In order to document the functionality and lock the expected behaviour, we should probably write some more tests.

提问题？
请把问题现象、相关日志、初步排查结果写清楚，即提供尽量多的线索，这样方便我们定位问题。

提建议？
请写明白建议原因，即为何有此建议。

提修复PR？
请说明为何做此修改，需要做好测试。

提Feature？
建议先将想法提出，不着急写代码，与社区同道沟通，大家觉得OK再做代码实现

I know documentation is a lot to ask for from an open-source project of this scale... but at least a formal notice on the SourceForge site somewhere would be pretty helpful.

When I download a release from a website and all it has is a text file pointing me somewhere else (with no mention on the actual site), I am (and should be) immediately suspicious that something has been compromised.

A l

WIth yarn 2 about to become stable, it comes with pnp enabled by default, so postinstall scripts now have one more downside. Having a postinstall script forces core-js to be duplicated on disk unnecessarily, reducing the efficiency of yarn install in pnp mode, which could otherwise potentially perform no writing to disk.

I know you don't want to remove the postinstall script, but just point

Depends on #4728 and #4729

• how it works
• why to do it / it creates a "seam" between blocking and async code
• examples of runtime safety checks associated with this feature

🚀 Feature request

To help with diagnosing ngcc issues it would be really useful to be able to see the debug output from ngcc. Could we expose these logs, perhaps when the CLI is in --verbose mode?

Command

• build
• serve
• test
• e2e

Tools such as docco and http://nevir.github.io/groc/index.html allow code and comments to be very nicely interspersed and prettily displayed in a browser. Since the code already has extensive comments / annotations, wouldn't it make sense to use something like this to improve viewing them further?

The doc/build folder should probably be included in the devdocs section of the real manual? If that's not suitable the folder should probably move elsewhere -- the doc folder only contains things related to the manual.

I'm currently developing an AutoML pipeline, in which I use the AutoML Step.
This link is the only place I was able to get to documentation regarding the AutoML step.

Looking around, I noticed that in the rc versions, AutoML was completely moved to