Skip to content

Schematics testing infrastructure: compare Trees, copy Trees #12707

Description

@natsid

Bug Report or Feature Request (mark with an x)

- [ ] bug report -> please search issues before submitting
- [x] feature request

Desired functionality

When unit testing a schematic or a rule, I have sometimes found that it would be convenient if I could take two trees and compare them. Or at least ask whether the two trees are equivalent.

As part of this, it would also be convenient if there was some Tree-copying function - specifically for checking that a Tree has not changed after some Rule call, but possibly for other cases as well.

Activity

  1. added this to the Backlog milestone on Oct 23, 2018
  2. angular-robot commented on Feb 1, 2022

    @angular-robot
    Contributor

    Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends.

    Find more details about Angular's feature request process in our documentation.

  3. modified the milestones: Backlog, needsTriage on Feb 1, 2022
  4. angular-robot commented on Feb 21, 2022

    @angular-robot
    Contributor

    Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage.

    We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package.

    You can find more details about the feature request process in our documentation.

  5. added
    feature: insufficient votesLabel to add when the not a sufficient number of votes or comments from unique authors
    and removed
    feature: votes requiredFeature request which is currently still in the voting phase
    on Feb 21, 2022
  6. alan-agius4 commented on Sep 24, 2026

    @alan-agius4
    Collaborator

    Thank you for taking the time to submit this feature request.

    At this time, we are not planning to implement this feature, as it did not gather sufficient community interest and we want to be mindful of expanding the CLI configuration surface area when existing workarounds are available.

    We will be closing this issue as not planned for now, though we are happy to reconsider it in the future if community interest changes.

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

    area: @angular-devkit/schematicsfeatureLabel used to distinguish feature request from other issuesfeature: insufficient votesLabel to add when the not a sufficient number of votes or comments from unique authors

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions