Skip to content

Transition to Angular Standalone Components in Favor of Angular Modules #378

Closed

Description

@Jefiozie

To align with modern Angular development practices, we propose migrating our project to use Angular Standalone Components. This transition aims to simplify our application architecture, improve modularity, and enhance developer experience.

Activity

  1. Harpush commented on Jan 21, 2024

    @Harpush
    Collaborator

    As a non breaking change first phase - we can transition to standalone but remain with an exported module importing and re-exporting the standalone components/directives.

    One other concern is we currently have multiple directives and components that are needed for the split to function. How will end users import those in a "bundle"? If I remember correctly exporting a const array still doesn't work from libraries.

  2. Jefiozie commented on Jan 23, 2024

    @Jefiozie
    ContributorAuthor

    I agree on the fact that we can easily do both for the current version. And when we bump to a major version remove the module.

    About the question, yes there is a problem with the import of standalone CMP /directives with an array. But there is also a workaround, we can use the spread operator to still import them. There is an ongoing issue that will fix the array without a spread operator.

  3. Harpush commented on Apr 29, 2024

    @Harpush
    Collaborator

    Just adding that we should introduce provideAngularSplit or provideAngularSplitOptions to allow using ANGULAR_SPLIT_DEFAULT_OPTIONS easier.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions