Feature requests are reviewed to align with existing projects on the Angular roadmap and then prioritized or voted through a 60-day process.

Chief editor, InfoWorld |

! [Angular team streamlines feature requests](https://images.idgesg.net/images/article/2019/02/thumbs-up_thumbs-down_good_bad_voting_opinion_compare_differe nt_positive_negative_by-comicsans-getty-100786977-large.jpg)Copy the code

ComicSans / Getty

The team behind Angular, Google’s popular typescript-based web framework, will soon introduce a new way to handle feature requests. The new approach will be similar to how Microsoft develops its Visual Studio Code editor.

In the new process, when a project receives a ticket, Angular team members review it and classify it as a feature request or problem. The team then verifies that the functional request is consistent with any existing projects on the roadmap. If it does, the request will be processed first. If not, it will be subject to a 60-day voting process.

[Also on InfoWorld: Angular 12 comes with a bunch of improvements].

During the voting period, anyone can vote for the feature by giving it a “thumbs up” response. If, at the end of 60 days, the feature has collected a certain number of votes, the team’s GitHub bot will tag it for consideration. Otherwise, the function will be turned off. Following a process set by Microsoft’s Visual Studio Code team, the Angular team considers requests with at least 20 votes and iterates if different votes provide a better result.

If a request has a tag to consider, it will be reviewed manually again. If the examiner verifies that the functionality is consistent with Angular’s vision for the future, the request is moved to the priority queue. If not, the request is closed with an explanation. Such functionality might be better suited to an external module, for example, built as an Angular extension.

Angular’s current process for handling feature requests recently required the team to stream more than 4,500 questions from GitHub and pull requests. Dealing with all these requests can be cumbersome and distracting to the team, failing to address the developer’s primary need. While tempting, it is unrealistic to include all functional requests. This can make the framework unlearnable and unmaintainable. But such feedback is “invaluable,” the team said in a May 27 announcement, two weeks after Angular 12 launched.

Paul Krill is the editor-in-chief of InfoWorld, where his coverage focuses on application development.

Copyright © 2021IDG Communications, Inc.