Issues: angular/angular
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
InjectionTokens which are intended to be multi-provided should have a Issues related to the framework runtime
readonly array type
area: core
Memory leak in RouterScroller class
area: router
memory leak
Issue related to a memory leak
P5
The team acknowledges the request but does not plan to address it, it remains open for discussion
Host directive input mapping not working in test environment
area: core
Issues related to the framework runtime
area: testing
Issues related to Angular testing features, such as TestBed
core: host directives
needs reproduction
This issue needs a reproduction in order for the team to investigate further
warn when default provider overrides custom provider.
area: core
Issues related to the framework runtime
Use Universal for angular.io
area: docs-infra
The angular.io application & related infra. Issues for docs content should use `area: docs`
lifecycle event should works if we create component as Embedded View Instead of HostView
area: core
Issues related to the framework runtime
feature: votes required
Feature request which is currently still in the voting phase
feature
Issue that requests a new feature
NullInjectorError: R3InjectorError(DynamicTestModule) When Testing with Standalone Component from Library
area: testing
Issues related to Angular testing features, such as TestBed
bug: bundled domino incorrectly returns undefined instead of null for querySelector
area: server
Issues related to server-side rendering
state: has PR
Non-imported standalone components combined with a directive are not reported during compilation
area: core
Issues related to the framework runtime
Nested computed signals have glitchy behavior due to garbage collection of WeakRef dependencies
area: core
Issues related to the framework runtime
core: reactivity
Work related to fine-grained reactivity in the core framework
cross-cutting: signals
FetchBackend call aborter.abort() in teardown logic even its observer closed.
area: common/http
needs reproduction
This issue needs a reproduction in order for the team to investigate further
Improvements for routerLink when used as hostDirective
area: router
router: directives
RouterLink, RouterLinkActive, RouterOutlet etc.
Undocumented Feature of ng-template: direct access to context
area: docs
Related to the documentation
Docs: call out CanDeactivate breaking change in v15 update guide
area: docs
Related to the documentation
Error NG0601 is reported incorrectly (triggered by NG0600) when calling toSignal inside a computed or effect
area: core
Issues related to the framework runtime
cross-cutting: signals
@Input and @Output bound to the same signal can produce an error
area: core
Issues related to the framework runtime
cross-cutting: signals
Force Universal to wait for component promises to resolve before rendering.
area: server
Issues related to server-side rendering
needs: clarification
This issue needs additional clarification from the reporter before the team can investigate.
all our unit test don't run anymore after upgrade from 15.2 to 16.1 of angular (NG0402)
area: testing
Issues related to Angular testing features, such as TestBed
FormControls are not usable in multiple formGroups
area: forms
forms: Controls API
Issues related to AbstractControl, FormControl, FormGroup, FormArray.
inject() vs constructor injection inconsistency for Pipes
area: core
Issues related to the framework runtime
bug
core: di
P3
An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Previous Next
ProTip!
Type g p on any issue or pull request to go back to the pull request listing page.