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

feat(lineage): fetch lineage with level and direction #157

Merged
merged 2 commits into from
Jul 12, 2022

Conversation

StewartJingga
Copy link
Contributor

No description provided.

@StewartJingga StewartJingga self-assigned this Jul 7, 2022
@StewartJingga StewartJingga linked an issue Jul 7, 2022 that may be closed by this pull request
@StewartJingga StewartJingga marked this pull request as ready for review July 7, 2022 11:46
@coveralls
Copy link

coveralls commented Jul 7, 2022

Pull Request Test Coverage Report for Build 2633912708

  • 88 of 114 (77.19%) changed or added relevant lines in 4 files are covered.
  • 1 unchanged line in 1 file lost coverage.
  • Overall coverage decreased (-0.2%) to 79.666%

Changes Missing Coverage Covered Lines Changed/Added Lines %
core/asset/service.go 0 2 0.0%
internal/server/v1beta1/lineage.go 6 8 75.0%
core/asset/lineage.go 0 6 0.0%
internal/store/postgres/lineage_repository.go 82 98 83.67%
Files with Coverage Reduction New Missed Lines %
core/asset/service.go 1 72.73%
Totals Coverage Status
Change from base Build 2507584689: -0.2%
Covered Lines: 4490
Relevant Lines: 5636

💛 - Coveralls

@StewartJingga StewartJingga merged commit ebbabe7 into main Jul 12, 2022
@StewartJingga StewartJingga deleted the lineage-control branch July 12, 2022 04:13
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.

feat: allow configure recursive level when fetching lineage
2 participants