-
Notifications
You must be signed in to change notification settings - Fork 9
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
feat: provide individual components for angular as standalone
components
#237
Comments
Actually this feature/option seems to be not fully implemented: |
I will give this issue a push since we ware st Angular 17 now. Standalone components are the recommended way in Angular now. Angular will drop or at least deprecate NgModules in the future. |
Another point: It produces less boilerplate code and makes integration and testing easier. |
@annsch the ticket that you've mentioned in here is closed – do you have a chance to review whether this is provided now and could you also provide some example for this or should somebody else take over ? |
If you give me a quick into about the mechanisms of mitosis here, I can probably also take over. |
BREAKING CHANGE: All Angular components are `standalone` now. SCAM (Single Component Angular Modules) have been removed. please import the standalone components directly in your `imports` section. ```ts app.component.ts //app.component.ts import { DBButton } from '@db-ui/ngx-components'; @component({ // ... imports: [ // ..., DBButton ], // ... }) ``` closes db-ui#237
@annsch I think I managed it. Fingers crossed. |
BREAKING CHANGE: All Angular components are `standalone` now. SCAM (Single Component Angular Modules) have been removed. please import the standalone components directly in your `imports` section. ```ts app.component.ts //app.component.ts import { DBButton } from '@db-ui/ngx-components'; @component({ // ... imports: [ // ..., DBButton ], // ... }) ``` closes db-ui#237
BREAKING CHANGE: All Angular components are `standalone` now. SCAM (Single Component Angular Modules) have been removed. please import the standalone components directly in your `imports` section. ```ts app.component.ts //app.component.ts import { DBButton } from '@db-ui/ngx-components'; @component({ // ... imports: [ // ..., DBButton ], // ... }) ``` closes db-ui#237
BREAKING CHANGE: All Angular components are `standalone` now. SCAM (Single Component Angular Modules) have been removed. please import the standalone components directly in your `imports` section. ```ts app.component.ts //app.component.ts import { DBButton } from '@db-ui/ngx-components'; @component({ // ... imports: [ // ..., DBButton ], // ... }) ``` closes db-ui#237
* refactor(ngx-components)!: completely switch to standalone BREAKING CHANGE: All Angular components are `standalone` now. SCAM (Single Component Angular Modules) have been removed. please import the standalone components directly in your `imports` section. ```ts app.component.ts //app.component.ts import { DBButton } from '@db-ui/ngx-components'; @component({ // ... imports: [ // ..., DBButton ], // ... }) ``` closes #237 * fix: use withHashLocation * fix: add missing NavigationContentDirective import * fix: add missing NavigationContentDirective import * fix: remove --ui flag from test * fix: add standalone for angular mitosis specific config as well
With the introduction of Standalone Components with Angular 14, components can be imported and tree-shaked individually without the need of a wrapping module such as
DBUIElementsModule
.It would be great if all components can be marked as
standalone
and imported individually.compare to db-ui/elements#605
The text was updated successfully, but these errors were encountered: