-
Notifications
You must be signed in to change notification settings - Fork 27.1k
Add extended diagnostics for @defer trigger misconfiguration #52739
Copy link
Copy link
Closed
Labels
area: coreIssues related to the framework runtimeIssues related to the framework runtimecore: deferIssues related to @defer blocks.Issues related to @defer blocks.featureLabel used to distinguish feature request from other issuesLabel used to distinguish feature request from other issuesfeature: in backlogFeature request for which voting has completed and is now in the backlogFeature request for which voting has completed and is now in the backlog
Milestone
Metadata
Metadata
Assignees
Labels
area: coreIssues related to the framework runtimeIssues related to the framework runtimecore: deferIssues related to @defer blocks.Issues related to @defer blocks.featureLabel used to distinguish feature request from other issuesLabel used to distinguish feature request from other issuesfeature: in backlogFeature request for which voting has completed and is now in the backlogFeature request for which voting has completed and is now in the backlog
Which @angular/* package(s) are relevant/related to the feature request?
core
Description
There are a few cases where a similar misconfiguration can happen, for example:
@defer (on immediate; on viewport; prefetch on idle)-- withon immediateother conditions do not make sense, since they'll never be triggered.@defer (on timer(5s); prefetch on timer(10s))-- the timer in the prefetch part would never be invoked to.There might be more cases like this. It'd be great to have an extended diagnostics that would detect this and output a warning.