You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which @angular/* package(s) are relevant/related to the feature request?
compiler
Description
We have a large application using a complex architecture of NgModules, that we would like to refactor into standalone components.
We are using primarily primeNG component library. In the most basic example below pInputText directive from that same library.
<inputtype="email" pInputText>
This requires the InputTextModule from primeNG, which in the original architecture is loaded into a SharedModule, but in the standalone components architecture InputTextModule needs to be imported in every component that uses the directive.
Proposed solution
Is there a way for the compiler to give warnings/errors if the template has directives that are not properly imported into the standalone component? This will help a lot with the refactoring to make sure we didn't miss importing any PrimeNG modules into the corresponding components.
Alternatives considered
Using text search to find all the uses of the directive is one way to do it... but very tedious and prone to errors if any file is missed by mistake.
The text was updated successfully, but these errors were encountered:
Which @angular/* package(s) are relevant/related to the feature request?
compiler
Description
We have a large application using a complex architecture of NgModules, that we would like to refactor into standalone components.
We are using primarily primeNG component library. In the most basic example below
pInputText
directive from that same library.This requires the
InputTextModule
from primeNG, which in the original architecture is loaded into a SharedModule, but in the standalone components architectureInputTextModule
needs to be imported in every component that uses the directive.Proposed solution
Is there a way for the compiler to give warnings/errors if the template has directives that are not properly imported into the standalone component? This will help a lot with the refactoring to make sure we didn't miss importing any PrimeNG modules into the corresponding components.
Alternatives considered
Using text search to find all the uses of the directive is one way to do it... but very tedious and prone to errors if any file is missed by mistake.
The text was updated successfully, but these errors were encountered: