Summary
Right now the Angular implementation of the library exports UiModule to a consuming app. This name is too vague and unspecific, and in many consuming projects there might be already an UiModule of their own.
What alternatives have you tried?
A consuming application can rename an import with as keyword, but UiModule of CVI may be imported multiple times (for example, into each feature module and into an app's Storybook), and keeping up with the necessity to rename each import is tiresome. And as a third party dependency, CVI should prefix its exported members.
Does this feature request involve any updates to the reference design?
No
Implementation details
No response
Summary
Right now the Angular implementation of the library exports
UiModuleto a consuming app. This name is too vague and unspecific, and in many consuming projects there might be already anUiModuleof their own.What alternatives have you tried?
A consuming application can rename an import with
askeyword, butUiModuleof CVI may be imported multiple times (for example, into each feature module and into an app's Storybook), and keeping up with the necessity to rename each import is tiresome. And as a third party dependency, CVI should prefix its exported members.Does this feature request involve any updates to the reference design?
No
Implementation details
No response