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

Change lineage positioning algorithm #18897

Merged
merged 6 commits into from
Dec 4, 2024
Merged

Change lineage positioning algorithm #18897

merged 6 commits into from
Dec 4, 2024

Conversation

karanh37
Copy link
Contributor

@karanh37 karanh37 commented Dec 3, 2024

Describe your changes:

Fixes

I worked on ... because ...

Before
Screenshot 2024-12-03 at 2 06 23 PM

After
Screenshot 2024-12-03 at 2 06 52 PM

Type of change:

  • Bug fix
  • Improvement
  • New feature
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation

Checklist:

  • I have read the CONTRIBUTING document.
  • My PR title is Fixes <issue-number>: <short explanation>
  • I have commented on my code, particularly in hard-to-understand areas.
  • For JSON Schema changes: I updated the migration scripts or explained why it is not needed.

Copy link
Contributor

github-actions bot commented Dec 3, 2024

Jest test Coverage

UI tests summary

Lines Statements Branches Functions
Coverage: 63%
63.69% (40285/63252) 40.16% (16043/39948) 42.58% (4800/11273)

Copy link

sonarqubecloud bot commented Dec 4, 2024

@karanh37 karanh37 merged commit fe661a2 into main Dec 4, 2024
16 of 18 checks passed
@karanh37 karanh37 deleted the lineage-reposition branch December 4, 2024 15:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
safe to test Add this label to run secure Github workflows on PRs UI UI specific issues
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants