Skip to content

explore other useful migration schematics to help with /zoneless adoption #576

Open

Description

@markgoho

the imports migration looks good, but we might be able to help folks out with other API migrations -- I'm manually migrating a bunch of specs right now, I'll see if anything pops out as an obvious win

Activity

  1. markgoho commented on Mar 26, 2026

    @markgoho
    ContributorAuthor

    a few that came up that might be worth investigating:

    • Rewrite simple inputs / componentInputs cases to bindings with inputBinding(...).
    • Rewrite output handler wiring (on-style cases) to Angular outputBinding(...).
    • Migrate component-scoped provider overrides to configureTestBed(...) + TestBed.overrideComponent(...).
    • Detect router-dependent components and add/suggest provideRouter([]) when moving to /zoneless.
    • Rewrite obvious ATL navigation-helper usage to the recommended zoneless routing pattern (or leave a targeted TODO).
  2. timdeschryver commented on Mar 31, 2026

    @timdeschryver
    Member

    @markgoho I think it's a good suggestion.
    If you want you can create a PR for one of these changes.

  3. markgoho commented on Mar 31, 2026

    @markgoho
    ContributorAuthor

    sure! I just need to familiarize myself with the migration system/syntax, and I can probably knock a few of these out

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions