@angular/* to v10 #5571 @hsuanxyzWithConfig @wendellhu95[nzKey] #2467, drag #3461 @hsuanxyzrefactor WithConfig
这是有什么新的想法吗?
refactor WithConfig
这是有什么新的想法吗?
现在的 API 要把默认值写在 WithConfig() 里面,很难看,而且打开 strict property initialization 检查之后之后 TypeScript 还会报错。
重构之后 WithConfig() 也不用带默认值了,看起来就跟平常的属性赋值一样。
话说 9.0 是马上要发布了吗?
话说 9.0 是马上要发布了吗?
已经发布
我发现是 cnpm 落后了,我去 sync 一下。
try to remove cdk backdrop
This requires some "click outside" mechanism. We can hack it or file a pull request to CDK.
try to remove cdk backdrop
This requires some "click outside" mechanism. We can hack it or file a pull request to CDK.
we need to resolve this issue https://github.com/NG-ZORRO/ng-zorro-antd/issues/4933 before implements click outside mechanism
Will you guys consider change how the new version be used ?
a suggestion:
today Angular 9.0 zorro 9.x
tomorrow Angular 10.0 zorro 10.0.x = 9.x (first support) 10.1.x = new feature
or
today Angualr 9.0 zorro 9.x
tomorrow Angular 10.0 zorro 9.99.x use 10.x for new feature
basicly , we create a new version with current feature just for use Angular's new feature, and next version for ng-zorror add new features
A nice way could be to have the x.0 release as the release that supports the latest version of Angular.
10.0 -> supports Angular 10
11.0 -> supports Angular 11
12.0 -> supports Angular 12
Then the x.1 to x.99 releases to have new functionality.
10.1 -> new functionality/bug fixes support on the Angular 10 supported version
10.2 -> new functionality/bug fixes support on the Angular 10 supported version
11.1 ->new functionality/bug fixes support on the Angular 11 supported version
etc.
In this way you decouple the effort needed to support new functionality AND a new update in one release.
Hi. When can we expect the new version released?
@hrvbernardic 10.0.0-beta.2 works well for me.
I'm waiting for Angular 11 with ivy language service now. Waiting ng-zorro-antd v11. lol.
@xiaoxiangmoe Same here, not complaining. Using beta 4. Just interested in some fixes on the table component I saw in commits.
Most helpful comment
A nice way could be to have the x.0 release as the release that supports the latest version of Angular.
Then the x.1 to x.99 releases to have new functionality.
In this way you decouple the effort needed to support new functionality AND a new update in one release.