On the way to Angular 9: Not only bug fixes in Angular 8.1
Although there is no specific information about Angular 9 yet, the work on the popular web framework continues, of course, despite the publication of Angular 8. As always, we stay on the ball and report continuously on the state of development of the framework. A first beta version for 8.1 has been released just a few days after the major, on board: a whole lot of bugfixes.
Angular 8, with polite delay, saw the light of day in June. But after the release is before the release and already in the autumn is Angular 9 on the plan, more precisely: in October or November, it should be ready. Whether this appointment is met, or Angular 9 is a gift from Nicholas? We will see. But until then it is still a long way and initially are the smaller releases, so Angular 8.1, 8.2, etc. into the house.
Angular 8.x: The minor releases
Angular 8.1.0-beta.0: Bug fixes and features planned
Update from 4 June 2019
On May 30, two days after the release of Angular 8, the first step was taken towards Angular 9. What is meant is that the first beta version of Angular 8.1 has been released, which already suggests a relatively large release: 30 bugs have been fixed to match the date. And that’s not all, because new features will also be included in the first minor release of the current release cycle — at least 6 in number.
One of the new features appeals especially to those developers who take care of the administration and have to make sure that everything is up-to-date: It will probably not be necessary to update flags with the file .bazelrc or the Toolchain related. Even platform flags for RBE builds and tests need to be updated from Angular 8.1 probably no longer extra. An exception, however, is when there are Braking Changes in Bazel that affect these flags. Instead, all you have to do is @bazel-toolchains the pin of the @bazel-toolchains repository in the packages/bazel/package.bzl file. rbe_autoconfig() way: If the rule rbe_autoconfig() in the repository @bazel_toolchains does not find a suitable toolchain configuration for the Bazel version, which is currently used by the respective project, it automatically pulls the appropriate container and generates the config at the beginning of the build or build . Testing.
Anyone using the SlicePipe transform methods can SlicePipe the new overloads that Angular 8.1 will SlicePipe . This should lead to the use of clearer types as always only any . However, this is accompanied by a Breaking Change, SlicePipe can be used from the update only with a number of values, a string, null or undefined .
In terms of bug fixes there was apparently a lot to fix after the update. Exactly 30 fixes were made in the first beta version of Angular 8.1. The focus was on Bazel, for example, in which context correct parameters are passed on to the http_server under Windows. But also at the core one screwed. The CSS Sanitizer now allows the use of parentheses in file names, which was previously not possible. In addition, an awkward bug was fixed, which ensured that not all files were taken during a migration. As many as seven bugs were fixed during the migration of static queries, among others it failed with preset default values of parameters and did not output errors correctly.
Please click here to see the list of bug fixes