Schematics testing infrastructure: compare Trees, copy Trees

Open
#12,707 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
testing, tooling

Research direction

Start by examining the schematics testing infrastructure and the Tree and Rule APIs referenced in the issue. Determine how tree equivalence and copying should behave, then add coverage showing that equivalent trees compare successfully and that a copied tree can be checked for changes after a rule call.

Written by the indexing model from the issue text.

Description

area: @angular-devkit/schematics feature feature: insufficient votes
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.

Dominant language
TypeScript
Stars
27k
Forks
11.8k
Avg merge
16h 35m
Merged PRs (30d)
176

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from angular/angular-cli

All issues in angular/angular-cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.