Skip to content
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

Default tests to tree-level conflicts #3746

Closed
wants to merge 2 commits into from

Conversation

ilyagr
Copy link
Collaborator

@ilyagr ilyagr commented May 24, 2024

This was essential for demoing #3223, or #2895, or maybe both.

Checklist

If applicable:

  • I have updated CHANGELOG.md
  • I have updated the documentation (README.md, docs/, demos/)
  • I have updated the config schema (cli/src/config-schema.json)
  • I have added tests to cover my changes

@ilyagr ilyagr changed the title Treedefault Default tests to tree-level conflicts May 24, 2024
@ilyagr ilyagr force-pushed the treedefault branch 2 times, most recently from 14e598e to ac9851f Compare May 24, 2024 02:42
Comment on lines -8 to -10
[format]
tree-level-conflicts = true

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we generally leave defaults in the file if possible so jj config list --include-defaults shows it.

@@ -50,7 +50,12 @@ fn diff_stream_equals_iter(tree1: &MergedTree, tree2: &MergedTree, matcher: &dyn

#[test]
fn test_from_legacy_tree() {
let test_repo = TestRepo::init();
// TODO: Find out why this test does not works with tree-level conflicts
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this test is explicitly about checking that an existing legacy tree can be read, but if we enable tree-level conflicts by defaults then the will be no legacy tree, right?

@ilyagr
Copy link
Collaborator Author

ilyagr commented Jun 13, 2024

I strongly suspect this was obsoleted by some recent PRs of Martin's.

@ilyagr ilyagr closed this Jun 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants