-
Notifications
You must be signed in to change notification settings - Fork 26.2k
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
NG0600 Error when using Mat Table DataSource, viewChild signals, and if-statements in Template
area: core
Issues related to the framework runtime
core: queries
core: reactivity
Work related to fine-grained reactivity in the core framework
state: needs more investigation
Attribute inside selector changed the input value in Angular@19
area: core
Issues related to the framework runtime
core: dynamic view creation
regression
Indicates than the issue relates to something that worked in a previous version
fix(core): avoid confusion between let value and internal data structures
action: review
The PR is still awaiting reviews from at least one requested reviewer
area: core
Issues related to the framework runtime
target: patch
This PR is targeted for the next patch release
Suggested workaround for content-projection in control flow blocks does not work
area: docs
Related to the documentation
hotlist: error messages
Dynamic component setInput does not respect internal input value changes (signal based inputs/model)
area: core
Issues related to the framework runtime
core: dynamic view creation
core: reactivity
Work related to fine-grained reactivity in the core framework
cross-cutting: signals
"Input is required but no value is available yet" with toObservable if the content is dynamic
area: core
Issues related to the framework runtime
area: forms
core: reactivity
Work related to fine-grained reactivity in the core framework
cross-cutting: signals
state: needs more investigation
[Feature Request] Subject Signal
area: core
Issues related to the framework runtime
core: reactivity
Work related to fine-grained reactivity in the core framework
core: rxjs interop
cross-cutting: signals
Automating Component Dependency Imports in Angular
area: core
Issues related to the framework runtime
cross-cutting: standalone
Issues related to the NgModule-less world
@angular/elements uses (internal) property name for custom element properties, but template name for attributes
area: elements
Issues related to Angular Elements
bug
cross-cutting: signals
P3
An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
new function for signal/rxjs interop
area: core
Issues related to the framework runtime
core: reactivity
Work related to fine-grained reactivity in the core framework
core: rxjs interop
cross-cutting: observables
cross-cutting: signals
hostDirectives
should auto-resolve double matching
area: core
Extending component with hostDirectives causes them to be matched twice
area: core
Issues related to the framework runtime
core: host directives
@for(ID of IDs; track ID) and NG0956 - provide a way to prevent warning when tracking by item is legit scenario
area: core
Issues related to the framework runtime
core: control flow
Issues related to the built-in control flow (@if, @for, @switch)
computed efficieny improvement
area: core
Issues related to the framework runtime
core: reactivity
Work related to fine-grained reactivity in the core framework
cross-cutting: signals
control flow schematics: projected content '<ng-content>' is not working post migration
area: migrations
Issues related to `ng update` migrations
core: control flow
Issues related to the built-in control flow (@if, @for, @switch)
state: needs more investigation
Performance regression in js web frameworks benchmark
area: performance
Issues related to performance
ngProjectedAs not working when used as static host property inside @Component
area: compiler
Issues related to `ngc`, Angular's template compiler
area: core
Issues related to the framework runtime
breaking changes
bug
core: content projection
hotlist: error messages
P4
A relatively minor issue that is not relevant to core functions
toSignal causes the signal to not being lazy-evaluated
area: core
Issues related to the framework runtime
core: reactivity
Work related to fine-grained reactivity in the core framework
core: rxjs interop
cross-cutting: signals
perf(core): short-circuit child queries
area: core
Issues related to the framework runtime
area: performance
Issues related to performance
state: blocked
target: patch
This PR is targeted for the next patch release
NG8011: Node matches the X slot of the Y component, but will not be projected into the specific slot because the surrounding @if has more than one node at its root.
area: compiler
Issues related to `ngc`, Angular's template compiler
area: core
Issues related to the framework runtime
core: control flow
Issues related to the built-in control flow (@if, @for, @switch)
Expand Control Flow to component dom elements
area: core
Issues related to the framework runtime
core: host and host bindings
Combination of Issues related to the framework runtime
core: host and host bindings
cross-cutting: signals
needs: discussion
Indicates than an issue is an open discussion
HostBinding
and signals is not supported (input signals too)
area: core
feat: ✨ Injecting EnvironmentProvider into component wrapped with @defer
area: core
Issues related to the framework runtime
core: defer
Issues related to @defer blocks.
core: di
needs: discussion
Indicates than an issue is an open discussion
After upgrade from angular 7 to 15 page rendering fails with error
area: core
Issues related to the framework runtime
bug
core: di
state: needs more investigation
Previous Next
ProTip!
Exclude everything labeled
bug
with -label:bug.