The entire Angular community and particularly what is left for the Angular group is moving down that road last year. It seems like there are no unicorns down here. We suppose you can stop. It is a period to stop pretending that anything is better.
What is the problem of Angular?
1. The Angular ecosystem falls apart
In recent years, the Angular group’s efforts were concentrated on operating on the run time, and compiler in the attempt to make up for the sad ending. In a similar period, some effort moved into using and assisting Bazel – the open-source toolchain’s version created particularly for Google.
In the end, Angular finished up parting ways with Bazel after many years of bad efforts to work like the better toolchain usable either inside or outside at Google.
A lot of components for those batteries including the app framework and programming language were moved to rot.
2. TSLint makes its final breath
Angular CLI equips with the tools’ preset. One of them can be TSLint. From TSLint deprecated, we might not expect the ecosystem with a fabulous tools’ set to even use it. Unluckily, it is even the case for the Angular CLI lint builder.
Next, ESLint assistance was implemented for Angular v10. Currently, we are left to know whether Angular might make it before the end of last year when TSLint stops admitting even security. Based on the Typescript’s creator, ESLint is quicker than TSLint and they get it for TypeScript itself.
3. Material of Angular is re-written
Angular Material is turning to implementations wrapping material design parts of the web, the framework-agnostic Google library. That is a wide range of work without observable distinction, realized from the outdoor perspective.
For a lot of parts, the Angular group will get less impact on the DOM structure. To mitigate it, they assisted with part test harnesses. If you get tests that can rely on the DOM texture of Angular material, you need to write again all the tests to make the library’s part harnesses or your tests might split during the Angular Material’s internals are substituted.
Component harnesses might be assisted by so-called harness environments. When the “Testbed Harness Environment” might operate with unit tests with other frameworks, Angular can convey with the “Protractor Harness Environment” for end tests.
4. Protractor releases a new version
Currently, the Angular group possesses Protractor. The Protractor was particularly touched in 2019 despite developing matters (around 200 open matters from 2019) and splitting changes in the APIs it wraps.
The Angular group controlled to cough up the Protractor v7 and bundle it with Angular v10. It feels that this version even assists the Webdriver API in communicating with more browsers.
5. No public roadmap
The particular promise of Ivy may fail to attract. Ivy is the enabler to what precisely? In recent years, the main framework has transformed as well.
Highly demanded attribute requests are even rejected like the non-framework issues, they get without response or they might not be laid out into the roadmap.
We believe that you can gain an insight into Angular struggles. Last but not least, if you have any questions, please ask us if needed.
Source: Lars Gyrup Brink Nielsen from Dev.to
Đọc thêm: Can IT Become A QA Tester With Non-It Background?
JT1 - IT Recruitment Agency
Điện thoại: +8428 6675 6685
Xem thêm các bài viết khác tại: https://www.jt1.vn/blog
Theo dõi chúng tôi tại: https://www.facebook.com/jt1asia/