dlin-cli 0.3.0a1__tar.gz → 0.3.0b1__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (348) hide show
  1. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/Cargo.lock +31 -3
  2. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/Cargo.toml +4 -3
  3. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/PKG-INFO +90 -5
  4. {dlin_cli-0.3.0a1/crates/dlin-core → dlin_cli-0.3.0b1}/README.md +89 -4
  5. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin/README.md +89 -4
  6. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin/src/cli/command.rs +19 -0
  7. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin/src/cli/common.rs +25 -5
  8. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin/src/cli/graph.rs +7 -1
  9. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin/src/cli/summary.rs +8 -2
  10. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin/src/commands/column.rs +6 -2
  11. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin/src/commands/graph.rs +28 -14
  12. dlin_cli-0.3.0b1/crates/dlin/src/commands/manifest.rs +446 -0
  13. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin/src/commands/mod.rs +4 -2
  14. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin/src/commands/shared.rs +130 -27
  15. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin/src/main.rs +1 -0
  16. dlin_cli-0.3.0b1/crates/dlin/src/mcp/column_result.rs +422 -0
  17. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin/src/mcp/mod.rs +2 -0
  18. dlin_cli-0.3.0b1/crates/dlin/src/mcp/page.rs +73 -0
  19. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin/src/mcp/protocol.rs +22 -4
  20. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin/src/mcp/tests.rs +291 -49
  21. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin/src/mcp/tools.rs +261 -119
  22. dlin_cli-0.3.0b1/crates/dlin/tests/integration/bigquery_lineage.rs +687 -0
  23. dlin_cli-0.3.0b1/crates/dlin/tests/integration/column_source_relation.rs +102 -0
  24. dlin_cli-0.3.0b1/crates/dlin/tests/integration/dependency_analysis.rs +323 -0
  25. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin/tests/integration/error_format.rs +3 -1
  26. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin/tests/integration/freshness.rs +237 -0
  27. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin/tests/integration/manifest_only.rs +29 -12
  28. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin/tests/integration_test.rs +6 -0
  29. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/ARCHITECTURE.md +59 -3
  30. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/Cargo.toml +2 -1
  31. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1/crates/dlin-core}/README.md +89 -4
  32. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/builder/mod.rs +83 -47
  33. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/builder/semantic_layer.rs +21 -1
  34. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/builder/tests/build_graph/dependency_analysis.rs +100 -7
  35. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/builder/tests/build_graph/semantic_layer.rs +50 -0
  36. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/column_lineage/backend/catalog_provider.rs +18 -1
  37. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/column_lineage/backend/sqllineage.rs +84 -14
  38. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/column_lineage/cross_model.rs +2 -1
  39. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/column_lineage/impact.rs +69 -6
  40. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/column_lineage/mod.rs +18 -3
  41. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/column_lineage/relation.rs +233 -2
  42. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/column_lineage/schema/context.rs +66 -11
  43. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/column_lineage/schema/evidence.rs +48 -0
  44. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/column_lineage/schema/mod.rs +24 -3
  45. dlin_cli-0.3.0b1/crates/dlin-core/src/graph/column_lineage/schema/seed_files.rs +258 -0
  46. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/column_lineage/tests/alias.rs +120 -2
  47. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/column_lineage/tests/backend_regression/mod.rs +1 -0
  48. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/column_lineage/tests/backend_regression/set_operations.rs +4 -2
  49. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/column_lineage/tests/cache.rs +25 -13
  50. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/column_lineage/tests/core_cross_model/mod.rs +9 -0
  51. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/column_lineage/tests/core_cross_model/scenarios.rs +24 -9
  52. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/column_lineage/tests/core_star.rs +1 -1
  53. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/column_lineage/tests/core_star_chain.rs +13 -0
  54. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/column_lineage/tests/core_util.rs +1 -0
  55. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/column_lineage/tests/evidence.rs +2 -2
  56. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/column_lineage/tests/impact/core.rs +6 -0
  57. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/column_lineage/tests/impact/edge_cases.rs +1 -0
  58. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/column_lineage/tests/impact/mod.rs +4 -0
  59. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/column_lineage/tests/impact/semantics.rs +54 -0
  60. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/column_lineage/tests/mod.rs +23 -0
  61. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/column_lineage/tests/output_slots.rs +1 -1
  62. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/column_lineage/tests/partial_lineage.rs +5 -2
  63. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/column_lineage/tests/production_output.rs +6 -6
  64. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/column_lineage/tests/regression_fixtures.rs +6 -6
  65. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/column_lineage/tests/schema_knowledge.rs +4 -4
  66. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/column_lineage/tests/yaml_schema.rs +2 -2
  67. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/column_lineage/types.rs +76 -15
  68. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/dependency/tests.rs +14 -0
  69. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/dependency.rs +130 -18
  70. dlin_cli-0.3.0b1/crates/dlin-core/src/graph/impact/exploration.rs +286 -0
  71. dlin_cli-0.3.0b1/crates/dlin-core/src/graph/impact/mod.rs +365 -0
  72. dlin_cli-0.3.0b1/crates/dlin-core/src/graph/impact/tests.rs +850 -0
  73. dlin_cli-0.3.0b1/crates/dlin-core/src/parser/jinja/interp/eval/adopt.rs +213 -0
  74. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/parser/jinja/interp/eval/builtins.rs +52 -7
  75. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/parser/jinja/interp/eval/expressions.rs +130 -20
  76. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/parser/jinja/interp/eval/methods.rs +110 -46
  77. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/parser/jinja/interp/eval/mod.rs +2 -0
  78. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/parser/jinja/interp/known.rs +9 -0
  79. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/parser/jinja/interp/tests.rs +213 -0
  80. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/parser/manifest/graph.rs +9 -4
  81. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/parser/manifest/mod.rs +129 -31
  82. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/parser/manifest/report/decode.rs +0 -2
  83. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/parser/manifest/report/mod.rs +37 -9
  84. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/parser/manifest/report/tests.rs +39 -7
  85. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/parser/manifest/tests/compatibility.rs +9 -5
  86. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/parser/manifest/tests/contents.rs +9 -0
  87. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/parser/manifest/tests/graph.rs +25 -0
  88. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/parser/manifest/tests/semantic_layer.rs +4 -0
  89. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/parser/manifest_cache.rs +13 -8
  90. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/parser/mod.rs +1 -0
  91. dlin_cli-0.3.0b1/crates/dlin-core/src/parser/package_roots.rs +65 -0
  92. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/parser/project.rs +17 -0
  93. dlin_cli-0.3.0b1/crates/dlin-core/src/render/dependency_diagnostics/tests.rs +290 -0
  94. dlin_cli-0.3.0b1/crates/dlin-core/src/render/dependency_diagnostics.rs +676 -0
  95. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/impact.rs +202 -16
  96. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/json.rs +8 -0
  97. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/list.rs +45 -2
  98. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/mod.rs +1 -0
  99. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__impact__tests__snapshot_impact_json.snap +29 -3
  100. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__impact__tests__snapshot_impact_json_with_sql.snap +29 -3
  101. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__impact__tests__snapshot_impact_text.snap +2 -0
  102. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__impact__tests__snapshot_impact_text_with_sql.snap +2 -0
  103. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__json__tests__snapshot_json_with_sql.snap +8 -0
  104. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__json__tests__snapshot_lineage.snap +20 -0
  105. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__json__tests__snapshot_node_metadata.snap +4 -0
  106. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__list__tests__snapshot_list_json.snap +20 -0
  107. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/summary.rs +41 -2
  108. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/tests/column_lineage_test.rs +20 -0
  109. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/src/build/expr.rs +15 -18
  110. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/src/build/function_semantics.rs +139 -8
  111. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/src/build/mod.rs +5 -0
  112. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/src/build/query.rs +1 -0
  113. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/src/build/select.rs +243 -7
  114. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/src/build/statement.rs +43 -10
  115. dlin_cli-0.3.0b1/crates/dlin-sqllineage/src/build/window.rs +97 -0
  116. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/src/catalog.rs +1 -0
  117. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/src/graph/scope.rs +47 -19
  118. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/src/ident.rs +24 -1
  119. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/src/keys.rs +44 -2
  120. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/src/output.rs +32 -0
  121. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/src/resolve/analysis.rs +31 -0
  122. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/src/resolve/binding.rs +1 -0
  123. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/src/resolve/model/build.rs +54 -26
  124. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/src/resolve/model/choose.rs +160 -23
  125. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/src/resolve/model/input.rs +153 -47
  126. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/src/resolve/model/join.rs +2 -0
  127. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/src/resolve/model/mod.rs +10 -3
  128. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/src/resolve/model/options.rs +1 -0
  129. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/src/resolve/model/tests.rs +21 -18
  130. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/src/resolve/star.rs +114 -8
  131. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/src/resolve/target.rs +3 -0
  132. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/src/types.rs +5 -0
  133. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/api.rs +7 -4
  134. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/binding_environment.rs +1 -0
  135. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/catalog.rs +3 -2
  136. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/catalog_knowledge.rs +8 -10
  137. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/catalog_resolution.rs +4 -0
  138. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/column_lineage.rs +1 -1
  139. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/common/mod.rs +28 -10
  140. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/correlated_names.rs +73 -5
  141. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/cte.rs +5 -3
  142. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/cyclic_references.rs +1 -0
  143. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/determinism.rs +34 -6
  144. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/direct_using_model.rs +48 -7
  145. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/evidence.rs +2 -1
  146. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/expected_lineage/identifiers.rs +32 -1
  147. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/expected_lineage/star_invariants.rs +1 -1
  148. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/expected_lineage/stars.rs +13 -14
  149. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/expected_lineage/support.rs +1 -0
  150. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/expr_coverage.rs +70 -2
  151. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/expression_value_inputs.rs +51 -1
  152. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/from_item_aliases.rs +1 -1
  153. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/identifier_keys.rs +13 -8
  154. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/merged_join_sources.rs +35 -10
  155. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/multi_hop_transform.rs +2 -2
  156. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/multi_statement.rs +3 -0
  157. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/name_providers.rs +96 -68
  158. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/output_identity.rs +2 -2
  159. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/qualifier_resolution.rs +3 -0
  160. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/regressions.rs +2 -2
  161. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/scope_reference_paths.rs +1 -1
  162. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/set_operation_operators.rs +1 -0
  163. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/set_operation_slots.rs +1 -0
  164. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/sqlparser_063.rs +10 -2
  165. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/table_lineage.rs +68 -0
  166. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/target_columns.rs +3 -0
  167. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/typed_identifiers.rs +1 -0
  168. dlin_cli-0.3.0b1/crates/dlin-sqllineage/tests/unaliased_unnest.rs +374 -0
  169. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/unmodelled_from_items.rs +1 -1
  170. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/virtual_value_inputs.rs +4 -2
  171. dlin_cli-0.3.0b1/crates/dlin-sqllineage/tests/window_functions.rs +185 -0
  172. dlin_cli-0.3.0a1/crates/dlin/src/commands/manifest.rs +0 -383
  173. dlin_cli-0.3.0a1/crates/dlin-core/src/graph/impact.rs +0 -535
  174. dlin_cli-0.3.0a1/crates/dlin-sqllineage/tests/window_functions.rs +0 -56
  175. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/LICENSE +0 -0
  176. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin/Cargo.toml +0 -0
  177. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin/src/cli/column.rs +0 -0
  178. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin/src/cli/misc.rs +0 -0
  179. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin/src/cli/mod.rs +0 -0
  180. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin/src/commands/debug.rs +0 -0
  181. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin/tests/integration/artifacts.rs +0 -0
  182. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin/tests/integration/cli.rs +0 -0
  183. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin/tests/integration/generic_test_metadata.rs +0 -0
  184. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin/tests/integration/manifest_only_rest.rs +0 -0
  185. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin/tests/integration/parsing.rs +0 -0
  186. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin/tests/integration/render_failure.rs +0 -0
  187. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin/tests/integration/sql_mode_test_warning.rs +0 -0
  188. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/error.rs +0 -0
  189. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/builder/project_yaml.rs +0 -0
  190. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/builder/tests/build_graph/basic.rs +0 -0
  191. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/builder/tests/build_graph/mod.rs +0 -0
  192. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/builder/tests/build_graph/project_gaps.rs +0 -0
  193. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/builder/tests/build_graph/yaml_snapshots.rs +0 -0
  194. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/builder/tests/generic_tests.rs +0 -0
  195. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/builder/tests/mod.rs +0 -0
  196. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/builder/tests/ref_parsing.rs +0 -0
  197. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/builder/tests/versioned.rs +0 -0
  198. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/column_lineage/backend/catalog.rs +0 -0
  199. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/column_lineage/backend/dialect.rs +0 -0
  200. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/column_lineage/backend/mod.rs +0 -0
  201. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/column_lineage/cache.rs +0 -0
  202. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/column_lineage/ident.rs +0 -0
  203. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/column_lineage/schema/sql_output.rs +0 -0
  204. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/column_lineage/tests/backend_regression/basic.rs +0 -0
  205. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/column_lineage/tests/backend_regression/discovery.rs +0 -0
  206. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/column_lineage/tests/core_basic.rs +0 -0
  207. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/filter/mod.rs +0 -0
  208. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/filter/tests/collapse.rs +0 -0
  209. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/filter/tests/filter_graph.rs +0 -0
  210. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/filter/tests/mod.rs +0 -0
  211. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/filter/tests/output.rs +0 -0
  212. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/filter/tests/search.rs +0 -0
  213. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/filter/tests/selector.rs +0 -0
  214. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/filter/tests/snapshots/dlin_core__graph__filter__tests__collapse__collapse_snapshot.snap +0 -0
  215. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/filter/tests/snapshots/dlin_core__graph__filter__tests__collapse__collapse_snapshot_bfs_pseudoendpoint.snap +0 -0
  216. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/filter/tests/snapshots/dlin_core__graph__filter__tests__collapse__collapse_snapshot_endpoints_fan_out.snap +0 -0
  217. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/filter/tests/snapshots/dlin_core__graph__filter__tests__collapse__collapse_snapshot_endpoints_leaf_model.snap +0 -0
  218. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/filter/tests/snapshots/dlin_core__graph__filter__tests__collapse__collapse_snapshot_multiple_focus_models.snap +0 -0
  219. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/filter/tests/snapshots/dlin_core__graph__filter__tests__collapse__collapse_snapshot_no_source_exposure.snap +0 -0
  220. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/filter/tests/snapshots/dlin_core__graph__filter__tests__collapse__collapse_snapshot_preserve_focus.snap +0 -0
  221. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/filter/tests/snapshots/dlin_core__graph__filter__tests__collapse__snapshot_transitive_node_type_filter.snap +0 -0
  222. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/filter/tests/snapshots/dlin_core__graph__filter__tests__collapse__snapshot_transitive_select_filter.snap +0 -0
  223. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/filter/tests/snapshots/dlin_core__graph__filter__tests__collapse__snapshot_transitive_select_with_node_type.snap +0 -0
  224. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/filter/tests/transitive.rs +0 -0
  225. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/filter/tests/versioned.rs +0 -0
  226. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/mod.rs +0 -0
  227. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/graph/types.rs +0 -0
  228. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/input.rs +0 -0
  229. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/lib.rs +0 -0
  230. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/parser/columns.rs +0 -0
  231. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/parser/discovery.rs +0 -0
  232. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/parser/jinja/interp/convert.rs +0 -0
  233. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/parser/jinja/interp/eval/calls.rs +0 -0
  234. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/parser/jinja/interp/eval/scan.rs +0 -0
  235. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/parser/jinja/interp/eval/statements.rs +0 -0
  236. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/parser/jinja/interp/ir.rs +0 -0
  237. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/parser/jinja/interp/library.rs +0 -0
  238. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/parser/jinja/interp/mod.rs +0 -0
  239. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/parser/jinja/interp/value.rs +0 -0
  240. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/parser/jinja/mod.rs +0 -0
  241. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/parser/manifest/tests/identifiers.rs +0 -0
  242. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/parser/manifest/tests/mod.rs +0 -0
  243. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/parser/sql/mod.rs +0 -0
  244. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/parser/sql/recovery.rs +0 -0
  245. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/parser/sql/tests.rs +0 -0
  246. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/parser/yaml_schema.rs +0 -0
  247. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/ascii.rs +0 -0
  248. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/column_graph.rs +0 -0
  249. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/column_graph_tests.rs +0 -0
  250. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/dot.rs +0 -0
  251. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/html.rs +0 -0
  252. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/layout.rs +0 -0
  253. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/mermaid.rs +0 -0
  254. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/plain.rs +0 -0
  255. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__column_graph__tests__dot_all_transformation_types.snap +0 -0
  256. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__column_graph__tests__dot_escapes_special_chars.snap +0 -0
  257. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__column_graph__tests__dot_id_collision_avoided.snap +0 -0
  258. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__column_graph__tests__dot_impact_indirect.snap +0 -0
  259. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__column_graph__tests__dot_impact_single.snap +0 -0
  260. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__column_graph__tests__dot_single_model.snap +0 -0
  261. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__column_graph__tests__dot_via_path.snap +0 -0
  262. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__column_graph__tests__impact_mermaid.snap +0 -0
  263. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__column_graph__tests__impact_mermaid_indirect_edge_label.snap +0 -0
  264. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__column_graph__tests__impact_plain.snap +0 -0
  265. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__column_graph__tests__impact_plain_multi_hop.snap +0 -0
  266. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__column_graph__tests__impact_plain_non_direct_intermediate.snap +0 -0
  267. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__column_graph__tests__mermaid_dotted_table_name.snap +0 -0
  268. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__column_graph__tests__mermaid_id_collision_avoided.snap +0 -0
  269. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__column_graph__tests__mermaid_label_escaping.snap +0 -0
  270. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__column_graph__tests__mermaid_single_model.snap +0 -0
  271. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__column_graph__tests__plain_model_path_non_direct_annotation.snap +0 -0
  272. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__column_graph__tests__plain_no_sources.snap +0 -0
  273. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__column_graph__tests__plain_single_model.snap +0 -0
  274. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__dot__tests__group_by_node_type.snap +0 -0
  275. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__dot__tests__snapshot_all_edge_types.snap +0 -0
  276. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__dot__tests__snapshot_direction_tb.snap +0 -0
  277. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__dot__tests__snapshot_direction_tb_grouped.snap +0 -0
  278. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__dot__tests__snapshot_group_by_directory.snap +0 -0
  279. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__dot__tests__snapshot_lineage.snap +0 -0
  280. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__dot__tests__snapshot_transitive_edges.snap +0 -0
  281. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__html__tests__snapshot_html_json.snap +0 -0
  282. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__list__tests__snapshot_list_plain.snap +0 -0
  283. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__mermaid__tests__group_by_node_type.snap +0 -0
  284. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__mermaid__tests__mixed_direct_and_transitive_edges.snap +0 -0
  285. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__mermaid__tests__show_columns_escapes_quotes.snap +0 -0
  286. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__mermaid__tests__show_columns_lineage.snap +0 -0
  287. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__mermaid__tests__show_columns_single_model.snap +0 -0
  288. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__mermaid__tests__show_columns_with_collapse.snap +0 -0
  289. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__mermaid__tests__show_columns_with_grouping.snap +0 -0
  290. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__mermaid__tests__snapshot_direction_tb.snap +0 -0
  291. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__mermaid__tests__snapshot_direction_tb_grouped.snap +0 -0
  292. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__mermaid__tests__snapshot_group_by_directory.snap +0 -0
  293. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__mermaid__tests__snapshot_lineage.snap +0 -0
  294. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__mermaid__tests__transitive_edge_rendering.snap +0 -0
  295. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__plain__tests__snapshot_plain.snap +0 -0
  296. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__summary__tests__snapshot_summary_json.snap +0 -0
  297. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/snapshots/dlin_core__render__summary__tests__snapshot_summary_text.snap +0 -0
  298. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/src/render/svg.rs +0 -0
  299. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-core/tests/structured_lineage_api.rs +0 -0
  300. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/ARCHITECTURE.md +0 -0
  301. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/Cargo.toml +0 -0
  302. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/LICENSE-APACHE +0 -0
  303. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/LICENSE-MIT +0 -0
  304. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/README.md +0 -0
  305. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/src/analyzer.rs +0 -0
  306. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/src/build/relation.rs +0 -0
  307. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/src/diagnostic.rs +0 -0
  308. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/src/dialect.rs +0 -0
  309. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/src/graph/edge.rs +0 -0
  310. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/src/graph/mod.rs +0 -0
  311. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/src/graph/node.rs +0 -0
  312. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/src/lib.rs +0 -0
  313. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/src/resolve/catalog.rs +0 -0
  314. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/src/resolve/context.rs +0 -0
  315. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/src/resolve/lineage.rs +0 -0
  316. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/src/resolve/mapping.rs +0 -0
  317. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/src/resolve/mod.rs +0 -0
  318. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/src/resolve/model/slot.rs +0 -0
  319. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/src/resolve/set_operation.rs +0 -0
  320. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/src/resolve/star/slot_eval/cut_tests.rs +0 -0
  321. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/src/resolve/star/slot_eval/forward_tests.rs +0 -0
  322. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/src/resolve/star/slot_eval/harness.rs +0 -0
  323. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/src/resolve/star/slot_eval/projection_tests.rs +0 -0
  324. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/src/resolve/star/slot_eval.rs +0 -0
  325. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/src/resolve/topo.rs +0 -0
  326. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/src/resolve/width.rs +0 -0
  327. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/aggregate_clauses.rs +0 -0
  328. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/by_name.rs +0 -0
  329. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/dialect.rs +0 -0
  330. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/expected_lineage/direct_using_inputs.rs +0 -0
  331. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/expected_lineage/direct_using_invariant_failures.json +0 -0
  332. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/expected_lineage/direct_using_invariant_skips.json +0 -0
  333. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/expected_lineage/direct_using_invariants.rs +0 -0
  334. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/expected_lineage/scopes_joins.rs +0 -0
  335. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/expected_lineage/star_invariant_failures.json +0 -0
  336. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/expected_lineage/target_columns.rs +0 -0
  337. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/expected_lineage.rs +0 -0
  338. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/join_merge.rs +0 -0
  339. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/lateral.rs +0 -0
  340. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/merge.rs +0 -0
  341. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/nested_empty_projection.rs +0 -0
  342. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/query_boundaries.rs +0 -0
  343. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/setexpr_coverage.rs +0 -0
  344. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/star_order.rs +0 -0
  345. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/star_positions.rs +0 -0
  346. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/table_query.rs +0 -0
  347. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/crates/dlin-sqllineage/tests/update.rs +0 -0
  348. {dlin_cli-0.3.0a1 → dlin_cli-0.3.0b1}/pyproject.toml +0 -0
@@ -228,9 +228,30 @@ version = "0.8.21"
228
228
  source = "registry+https://github.com/rust-lang/crates.io-index"
229
229
  checksum = "d0a5c400df2834b80a4c3327b3aad3a4c4cd4de0629063962b03235697506a28"
230
230
 
231
+ [[package]]
232
+ name = "csv"
233
+ version = "1.4.0"
234
+ source = "registry+https://github.com/rust-lang/crates.io-index"
235
+ checksum = "52cd9d68cf7efc6ddfaaee42e7288d3a99d613d4b50f76ce9827ae0c6e14f938"
236
+ dependencies = [
237
+ "csv-core",
238
+ "itoa",
239
+ "ryu",
240
+ "serde_core",
241
+ ]
242
+
243
+ [[package]]
244
+ name = "csv-core"
245
+ version = "0.1.13"
246
+ source = "registry+https://github.com/rust-lang/crates.io-index"
247
+ checksum = "704a3c26996a80471189265814dbc2c257598b96b8a7feae2d31ace646bb9782"
248
+ dependencies = [
249
+ "memchr",
250
+ ]
251
+
231
252
  [[package]]
232
253
  name = "dlin"
233
- version = "0.3.0-alpha.1"
254
+ version = "0.3.0-beta.1"
234
255
  dependencies = [
235
256
  "anyhow",
236
257
  "clap",
@@ -248,11 +269,12 @@ dependencies = [
248
269
 
249
270
  [[package]]
250
271
  name = "dlin-core"
251
- version = "0.3.0-alpha.1"
272
+ version = "0.3.0-beta.1"
252
273
  dependencies = [
253
274
  "anyhow",
254
275
  "clap",
255
276
  "colored",
277
+ "csv",
256
278
  "dlin-sqllineage",
257
279
  "filetime",
258
280
  "globset",
@@ -275,7 +297,7 @@ dependencies = [
275
297
 
276
298
  [[package]]
277
299
  name = "dlin-sqllineage"
278
- version = "0.3.0-alpha.1"
300
+ version = "0.3.0-beta.1"
279
301
  dependencies = [
280
302
  "indexmap",
281
303
  "serde",
@@ -750,6 +772,12 @@ dependencies = [
750
772
  "windows-sys",
751
773
  ]
752
774
 
775
+ [[package]]
776
+ name = "ryu"
777
+ version = "1.0.23"
778
+ source = "registry+https://github.com/rust-lang/crates.io-index"
779
+ checksum = "9774ba4a74de5f7b1c1451ed6cd5285a32eddb5cccb8cc655a4e50009e06477f"
780
+
753
781
  [[package]]
754
782
  name = "same-file"
755
783
  version = "1.0.6"
@@ -3,7 +3,7 @@ members = ["crates/*"]
3
3
  resolver = "3"
4
4
 
5
5
  [workspace.package]
6
- version = "0.3.0-alpha.1"
6
+ version = "0.3.0-beta.1"
7
7
  edition = "2024"
8
8
  license = "MIT"
9
9
  repository = "https://github.com/eitsupi/dlin"
@@ -27,6 +27,7 @@ globset = "0.4"
27
27
  # SQL parsing and AST metadata stay inside dlin-sqllineage.
28
28
  sqlparser = { version = "0.64", features = ["serde", "visitor"] }
29
29
  path-slash = "0.2.1"
30
+ csv = "1"
30
31
  clap = { version = "4", features = ["derive", "env"] }
31
32
  libc = "0.2"
32
33
 
@@ -37,8 +38,8 @@ insta = "1"
37
38
  serial_test = "4.0.1"
38
39
 
39
40
  # internal
40
- dlin-core = { version = "0.3.0-alpha.1", path = "crates/dlin-core" }
41
- sqllineage = { package = "dlin-sqllineage", version = "0.3.0-alpha.1", path = "crates/dlin-sqllineage" }
41
+ dlin-core = { version = "0.3.0-alpha.2", path = "crates/dlin-core" }
42
+ sqllineage = { package = "dlin-sqllineage", version = "0.3.0-alpha.2", path = "crates/dlin-sqllineage" }
42
43
 
43
44
  [workspace.lints.rust]
44
45
  unexpected_cfgs = { level = "warn", check-cfg = ['cfg(tarpaulin_include)'] }
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: dlin-cli
3
- Version: 0.3.0a1
3
+ Version: 0.3.0b1
4
4
  Classifier: Development Status :: 4 - Beta
5
5
  Classifier: Environment :: Console
6
6
  Classifier: Intended Audience :: Developers
@@ -114,7 +114,7 @@ For model-name inputs, `manifest.json` is the only file needed in manifest mode.
114
114
  - `var()` resolves from `vars.yml` or `dbt_project.yml`, then its default (`--vars` CLI overrides not supported)
115
115
  - `env_var()` uses its default and never reads the environment. A different value at run time can select a different dependency or branch than the one shown
116
116
  - Values known only at run time (`target`, `env_var()` without a default, `run_query()` results) do not select dependencies; `execute` is false, as when dbt parses the project
117
- - Dependencies selected through `adapter.dispatch()` or namespaced package macros (e.g. `dbt_utils.*`) may be missed
117
+ - Dependencies selected through `adapter.dispatch()` or namespaced package macros (e.g. `dbt_utils.*`) may be missed. The nodes concerned are reported as partial (see [Completeness of model-level dependencies](#completeness-of-model-level-dependencies))
118
118
  - Generic test IDs are dlin-specific (e.g. `test.not_null.orders.order_id`) and do not match dbt's naming; use manifest mode when exact test IDs matter
119
119
 
120
120
  When these limitations matter, use `--source manifest`.
@@ -156,7 +156,7 @@ For analysts and agents who work from a distributed `manifest.json` without acce
156
156
  dlin mcp --manifest-path path/to/manifest.json
157
157
  ```
158
158
 
159
- Available MCP tools: project summary, model search, lineage, impact analysis, and column-level lineage.
159
+ Tools return compact JSON as a single text result. Use `get_project_summary` to check manifest freshness and loading diagnostics. Lineage and impact results distinguish confirmed paths from possible paths and show where analysis could not continue. Request `detail: "full"` for paths and evidence, or follow `page.next_cursor` with the same query for more rows. Use `include_sql: true` with `find_nodes` to request compiled SQL.
160
160
 
161
161
  The SQL dialect for column lineage is detected from the manifest's `adapter_type`; `--dialect` overrides it. Requires a compiled `manifest.json` (`dbt compile`).
162
162
 
@@ -337,9 +337,9 @@ dlin column upstream customers --column order_count --column lifetime_value -o p
337
337
 
338
338
  ```
339
339
  customers (2 columns listed: 2 complete, 0 partial)
340
- order_count → orders.id → stg_orders.order_id → orders.order_id (aggregation)
340
+ order_count → raw.orders.id → stg_orders.order_id → orders.order_id (aggregation)
341
341
  boundary: external relation at stg_orders.order_id for customers.order_count: raw.orders (source, policy: snapshot unsupported; seed external)
342
- lifetime_value → payments.amount → stg_payments.amount → orders.total_amount (aggregation)
342
+ lifetime_value → raw.payments.amount → stg_payments.amount → orders.total_amount (aggregation)
343
343
  boundary: external relation at stg_payments.amount for customers.lifetime_value: raw.payments (source, policy: snapshot unsupported; seed external)
344
344
  assumes yaml:source.clp.raw.orders (YAML columns taken as exhaustive): order_count
345
345
  assumes yaml:source.clp.raw.payments (YAML columns taken as exhaustive): lifetime_value
@@ -435,6 +435,91 @@ Impacted Nodes:
435
435
  [low ] assert_orders_positive_amount (test, distance: 1)
436
436
  ```
437
437
 
438
+ ### Completeness of model-level dependencies
439
+
440
+ dlin reports where it could not analyse the model-level dependencies (`ref()`, `source()`, tests, exposures), so a program can tell whether a result may be missing something.
441
+
442
+ - **Each node** has `dependency_analysis` in `list` JSON (by default), in `graph` JSON (with `--json-full` or `--json-fields dependency_analysis`) and in `impact` JSON. Its `status` is `complete` or `partial`; `unresolved` lists a typed reason for each part that could not be analysed. `complete` means that, under dlin's evaluation rules, no part was left unresolved. In particular, `env_var()` is evaluated with its default, so a different value at run time can select another dependency; check run-time dependencies with a manifest generated for that environment.
443
+ - **Each impact report** has `exploration`, which says whether the reached nodes can be missing a node. It is `complete` only when no node outside the reached set has reasons (phantom nodes, which stand for unresolved targets, are left out; the nodes referencing them carry the reasons), no input was skipped and no scope went unassessed. Otherwise `gaps` lists why. An empty `exploration` means the search did not run, as for an input that is an unresolved reference. Manifest mode takes the manifest's dependencies as they are, so its exploration is always incomplete with `not_assessed` (`manifest_dependencies`).
444
+ - `complete` concerns the reached set only. It does not confirm that each reached node is affected, nor the distances or paths. It is relative to the project and the paths it configures: a configured path that does not exist is a warning, not a gap.
445
+ - A node whose analysis is `complete` says nothing about the project as a whole: an input that could not be read is not attributed to any node. Do not conclude that a project is fully analysed because every listed node is `complete`.
446
+ - A reason states that something was not analysed, not that a dependency is missing.
447
+
448
+ On stderr, a command that builds the graph prints, once and before any filtering:
449
+
450
+ - at most one configuration warning, such as a path in `dbt_project.yml` that does not exist;
451
+ - one `dependency_analysis_summary` when any node has reasons or any project gap remains. It counts the whole project: `partial_nodes` (as in node JSON), `not_assessed_nodes` (the partial nodes whose only reasons are `not_assessed`), reasons by type and namespace, and project gaps. It is a warning when a node is partially analysed or an input was skipped, and info when only scopes are not assessed, as in manifest mode. It is not the exploration of any impact report.
452
+
453
+ `--verbose` adds one diagnostic per reason, with its node and call site, one per project gap, and the info diagnostics for default paths that do not exist. `--quiet` suppresses all of them. With `--error-format json`, these diagnostics carry a `code` and typed fields next to `level`, `what`, `why` and `hint`; read the code and the fields, not the text.
454
+
455
+ #### Using impact in CI
456
+
457
+ To accept "no impact" only when it is proved, check every condition, not only an empty `impacted_nodes`. The first definition rejects an exploration whose `status` and `gaps` disagree:
458
+
459
+ ```sh
460
+ dlin impact orders -o json -q > impact.json && jq -e --arg id model.orders '
461
+ def consistent:
462
+ (.gaps | type == "array")
463
+ and ((.status == "complete" and (.gaps | length == 0))
464
+ or (.status == "incomplete" and (.gaps | length > 0)));
465
+ def model_explorations: [.exploration[] | select(.kind == "model_dependency")];
466
+ length == 1
467
+ and (.[0] | .source_node.unique_id == $id
468
+ and (.impacted_nodes | type == "array" and length == 0)
469
+ and (model_explorations | length > 0
470
+ and all(.[]; consistent and .status == "complete")))
471
+ ' impact.json
472
+ ```
473
+
474
+ Checking `source_node.unique_id` catches an input that did not resolve to the node you meant; with several inputs, check each report. `impact` succeeds as long as one input is found, and its exit code does not depend on completeness.
475
+
476
+ You may decide, after checking them, that some reasons do not hide a dependency in your project. To proceed despite them, accept a gap only when every one of its reasons matches a rule you have checked, and reject everything else, including reason and gap types you do not know. For example, to accept calls through the `dbt` namespace:
477
+
478
+ ```sh
479
+ jq -e --arg id model.orders '
480
+ def consistent:
481
+ (.gaps | type == "array")
482
+ and ((.status == "complete" and (.gaps | length == 0))
483
+ or (.status == "incomplete" and (.gaps | length > 0)));
484
+ def accepted:
485
+ .type == "unresolved_dependencies"
486
+ and (.reasons | type == "array" and length > 0)
487
+ and all(.reasons[]; .type == "unsupported_macro_namespace" and .namespace == "dbt");
488
+ def model_explorations: [.exploration[] | select(.kind == "model_dependency")];
489
+ length == 1
490
+ and (.[0] | .source_node.unique_id == $id
491
+ and (model_explorations | length > 0
492
+ and all(.[]; consistent and all(.gaps[]; accepted))))
493
+ ' impact.json
494
+ ```
495
+
496
+ Accepting gaps is a decision to take the risk; it does not prove that the change has no impact. The `namespace` is the name written in the call, not the package that owns the macro, so a namespace alone does not make a call safe. Before accepting a rule, check that the macro and the macros it calls read no `ref()` or `source()`, and that no argument, branch or dispatch inside them selects a dependency.
497
+
498
+ In the table, *miss* means the graph may lack a dependency, and *wrong edge* that an edge dlin kept may not be the one dbt uses.
499
+
500
+ | Reason `type` | Meaning | May | Check |
501
+ | --- | --- | --- | --- |
502
+ | `unresolved_ref`, `unresolved_source` | The target could not be resolved in the searched paths | miss | The name, or that its file is in a searched path |
503
+ | `invalid_dependency_call` | `ref()` or `source()` with arguments that are not valid | miss | The call |
504
+ | `generic_test_body_not_analyzed` | The body of a generic test macro is not analysed; its YAML arguments are evaluated, and may carry reasons of their own | miss | Whether the test macro reads other models |
505
+ | `unsupported_dependency_expression`, `dependency_target_missing` | An exposure `depends_on` entry that is not supported or names nothing | miss | The entry |
506
+ | `unresolved_var` | A `var()` without a value or default selects a dependency | miss, wrong edge | Set the variable or give a default |
507
+ | `runtime_value_unknown` | A value known only when dbt runs (`target`, `env_var()` without a default, `run_query()`, ...) selects a dependency | miss, wrong edge | A manifest generated for that environment |
508
+ | `unsupported_dispatch` | `adapter.dispatch()` is not resolved | miss, wrong edge | The dispatched implementations |
509
+ | `unsupported_macro_namespace` | A macro called through a namespace (`dbt_utils.star()`, `dbt.type_string()`) is not analysed | miss, wrong edge | That macro, as described above |
510
+ | `unresolved_call` | A call whose callee could not be identified | miss, wrong edge | That the macro is defined in a searched path |
511
+ | `macro_reachability_unknown` | The macros a call can reach could not be determined | miss, wrong edge | Which macro the call selects |
512
+ | `unsupported_jinja_construct` | A Jinja construct the analysis does not model | miss, wrong edge | That part of the template |
513
+ | `jinja_render_failed` | The template could not be interpreted | miss, wrong edge | The template syntax |
514
+ | `analysis_limit_reached` | The analysis stopped at a recursion or work limit | miss, wrong edge | Deeply recursive macros |
515
+ | `unsupported_ref_package` | A `ref()` naming a package, resolved by name only | miss, wrong edge | That the edge goes to the intended node |
516
+ | `ambiguous_ref` | A `ref()` matching several nodes (`candidates`); the edge goes to one of them | miss, wrong edge | Rename one of them |
517
+ | `not_assessed` | The node's dependencies are not assessed at all (`scope`: `manifest_dependencies`, `semantic_dependencies`, or `phantom_dependencies` on phantom nodes, which is never a gap) | anything | |
518
+
519
+ A reason does not establish that an edge is wrong or that one is missing. Literal `ref()` calls under a condition dlin cannot evaluate still produce edges, so `impacted_nodes` may include nodes that are not affected.
520
+
521
+ A skipped input (`input_skipped`: a file that could not be listed, read or parsed) belongs to no node. Besides the dependencies it holds, it can change how names and macros resolve elsewhere, so it is a gap of every exploration that ran.
522
+
438
523
  ## Filtering
439
524
 
440
525
  ```sh
@@ -92,7 +92,7 @@ For model-name inputs, `manifest.json` is the only file needed in manifest mode.
92
92
  - `var()` resolves from `vars.yml` or `dbt_project.yml`, then its default (`--vars` CLI overrides not supported)
93
93
  - `env_var()` uses its default and never reads the environment. A different value at run time can select a different dependency or branch than the one shown
94
94
  - Values known only at run time (`target`, `env_var()` without a default, `run_query()` results) do not select dependencies; `execute` is false, as when dbt parses the project
95
- - Dependencies selected through `adapter.dispatch()` or namespaced package macros (e.g. `dbt_utils.*`) may be missed
95
+ - Dependencies selected through `adapter.dispatch()` or namespaced package macros (e.g. `dbt_utils.*`) may be missed. The nodes concerned are reported as partial (see [Completeness of model-level dependencies](#completeness-of-model-level-dependencies))
96
96
  - Generic test IDs are dlin-specific (e.g. `test.not_null.orders.order_id`) and do not match dbt's naming; use manifest mode when exact test IDs matter
97
97
 
98
98
  When these limitations matter, use `--source manifest`.
@@ -134,7 +134,7 @@ For analysts and agents who work from a distributed `manifest.json` without acce
134
134
  dlin mcp --manifest-path path/to/manifest.json
135
135
  ```
136
136
 
137
- Available MCP tools: project summary, model search, lineage, impact analysis, and column-level lineage.
137
+ Tools return compact JSON as a single text result. Use `get_project_summary` to check manifest freshness and loading diagnostics. Lineage and impact results distinguish confirmed paths from possible paths and show where analysis could not continue. Request `detail: "full"` for paths and evidence, or follow `page.next_cursor` with the same query for more rows. Use `include_sql: true` with `find_nodes` to request compiled SQL.
138
138
 
139
139
  The SQL dialect for column lineage is detected from the manifest's `adapter_type`; `--dialect` overrides it. Requires a compiled `manifest.json` (`dbt compile`).
140
140
 
@@ -315,9 +315,9 @@ dlin column upstream customers --column order_count --column lifetime_value -o p
315
315
 
316
316
  ```
317
317
  customers (2 columns listed: 2 complete, 0 partial)
318
- order_count → orders.id → stg_orders.order_id → orders.order_id (aggregation)
318
+ order_count → raw.orders.id → stg_orders.order_id → orders.order_id (aggregation)
319
319
  boundary: external relation at stg_orders.order_id for customers.order_count: raw.orders (source, policy: snapshot unsupported; seed external)
320
- lifetime_value → payments.amount → stg_payments.amount → orders.total_amount (aggregation)
320
+ lifetime_value → raw.payments.amount → stg_payments.amount → orders.total_amount (aggregation)
321
321
  boundary: external relation at stg_payments.amount for customers.lifetime_value: raw.payments (source, policy: snapshot unsupported; seed external)
322
322
  assumes yaml:source.clp.raw.orders (YAML columns taken as exhaustive): order_count
323
323
  assumes yaml:source.clp.raw.payments (YAML columns taken as exhaustive): lifetime_value
@@ -413,6 +413,91 @@ Impacted Nodes:
413
413
  [low ] assert_orders_positive_amount (test, distance: 1)
414
414
  ```
415
415
 
416
+ ### Completeness of model-level dependencies
417
+
418
+ dlin reports where it could not analyse the model-level dependencies (`ref()`, `source()`, tests, exposures), so a program can tell whether a result may be missing something.
419
+
420
+ - **Each node** has `dependency_analysis` in `list` JSON (by default), in `graph` JSON (with `--json-full` or `--json-fields dependency_analysis`) and in `impact` JSON. Its `status` is `complete` or `partial`; `unresolved` lists a typed reason for each part that could not be analysed. `complete` means that, under dlin's evaluation rules, no part was left unresolved. In particular, `env_var()` is evaluated with its default, so a different value at run time can select another dependency; check run-time dependencies with a manifest generated for that environment.
421
+ - **Each impact report** has `exploration`, which says whether the reached nodes can be missing a node. It is `complete` only when no node outside the reached set has reasons (phantom nodes, which stand for unresolved targets, are left out; the nodes referencing them carry the reasons), no input was skipped and no scope went unassessed. Otherwise `gaps` lists why. An empty `exploration` means the search did not run, as for an input that is an unresolved reference. Manifest mode takes the manifest's dependencies as they are, so its exploration is always incomplete with `not_assessed` (`manifest_dependencies`).
422
+ - `complete` concerns the reached set only. It does not confirm that each reached node is affected, nor the distances or paths. It is relative to the project and the paths it configures: a configured path that does not exist is a warning, not a gap.
423
+ - A node whose analysis is `complete` says nothing about the project as a whole: an input that could not be read is not attributed to any node. Do not conclude that a project is fully analysed because every listed node is `complete`.
424
+ - A reason states that something was not analysed, not that a dependency is missing.
425
+
426
+ On stderr, a command that builds the graph prints, once and before any filtering:
427
+
428
+ - at most one configuration warning, such as a path in `dbt_project.yml` that does not exist;
429
+ - one `dependency_analysis_summary` when any node has reasons or any project gap remains. It counts the whole project: `partial_nodes` (as in node JSON), `not_assessed_nodes` (the partial nodes whose only reasons are `not_assessed`), reasons by type and namespace, and project gaps. It is a warning when a node is partially analysed or an input was skipped, and info when only scopes are not assessed, as in manifest mode. It is not the exploration of any impact report.
430
+
431
+ `--verbose` adds one diagnostic per reason, with its node and call site, one per project gap, and the info diagnostics for default paths that do not exist. `--quiet` suppresses all of them. With `--error-format json`, these diagnostics carry a `code` and typed fields next to `level`, `what`, `why` and `hint`; read the code and the fields, not the text.
432
+
433
+ #### Using impact in CI
434
+
435
+ To accept "no impact" only when it is proved, check every condition, not only an empty `impacted_nodes`. The first definition rejects an exploration whose `status` and `gaps` disagree:
436
+
437
+ ```sh
438
+ dlin impact orders -o json -q > impact.json && jq -e --arg id model.orders '
439
+ def consistent:
440
+ (.gaps | type == "array")
441
+ and ((.status == "complete" and (.gaps | length == 0))
442
+ or (.status == "incomplete" and (.gaps | length > 0)));
443
+ def model_explorations: [.exploration[] | select(.kind == "model_dependency")];
444
+ length == 1
445
+ and (.[0] | .source_node.unique_id == $id
446
+ and (.impacted_nodes | type == "array" and length == 0)
447
+ and (model_explorations | length > 0
448
+ and all(.[]; consistent and .status == "complete")))
449
+ ' impact.json
450
+ ```
451
+
452
+ Checking `source_node.unique_id` catches an input that did not resolve to the node you meant; with several inputs, check each report. `impact` succeeds as long as one input is found, and its exit code does not depend on completeness.
453
+
454
+ You may decide, after checking them, that some reasons do not hide a dependency in your project. To proceed despite them, accept a gap only when every one of its reasons matches a rule you have checked, and reject everything else, including reason and gap types you do not know. For example, to accept calls through the `dbt` namespace:
455
+
456
+ ```sh
457
+ jq -e --arg id model.orders '
458
+ def consistent:
459
+ (.gaps | type == "array")
460
+ and ((.status == "complete" and (.gaps | length == 0))
461
+ or (.status == "incomplete" and (.gaps | length > 0)));
462
+ def accepted:
463
+ .type == "unresolved_dependencies"
464
+ and (.reasons | type == "array" and length > 0)
465
+ and all(.reasons[]; .type == "unsupported_macro_namespace" and .namespace == "dbt");
466
+ def model_explorations: [.exploration[] | select(.kind == "model_dependency")];
467
+ length == 1
468
+ and (.[0] | .source_node.unique_id == $id
469
+ and (model_explorations | length > 0
470
+ and all(.[]; consistent and all(.gaps[]; accepted))))
471
+ ' impact.json
472
+ ```
473
+
474
+ Accepting gaps is a decision to take the risk; it does not prove that the change has no impact. The `namespace` is the name written in the call, not the package that owns the macro, so a namespace alone does not make a call safe. Before accepting a rule, check that the macro and the macros it calls read no `ref()` or `source()`, and that no argument, branch or dispatch inside them selects a dependency.
475
+
476
+ In the table, *miss* means the graph may lack a dependency, and *wrong edge* that an edge dlin kept may not be the one dbt uses.
477
+
478
+ | Reason `type` | Meaning | May | Check |
479
+ | --- | --- | --- | --- |
480
+ | `unresolved_ref`, `unresolved_source` | The target could not be resolved in the searched paths | miss | The name, or that its file is in a searched path |
481
+ | `invalid_dependency_call` | `ref()` or `source()` with arguments that are not valid | miss | The call |
482
+ | `generic_test_body_not_analyzed` | The body of a generic test macro is not analysed; its YAML arguments are evaluated, and may carry reasons of their own | miss | Whether the test macro reads other models |
483
+ | `unsupported_dependency_expression`, `dependency_target_missing` | An exposure `depends_on` entry that is not supported or names nothing | miss | The entry |
484
+ | `unresolved_var` | A `var()` without a value or default selects a dependency | miss, wrong edge | Set the variable or give a default |
485
+ | `runtime_value_unknown` | A value known only when dbt runs (`target`, `env_var()` without a default, `run_query()`, ...) selects a dependency | miss, wrong edge | A manifest generated for that environment |
486
+ | `unsupported_dispatch` | `adapter.dispatch()` is not resolved | miss, wrong edge | The dispatched implementations |
487
+ | `unsupported_macro_namespace` | A macro called through a namespace (`dbt_utils.star()`, `dbt.type_string()`) is not analysed | miss, wrong edge | That macro, as described above |
488
+ | `unresolved_call` | A call whose callee could not be identified | miss, wrong edge | That the macro is defined in a searched path |
489
+ | `macro_reachability_unknown` | The macros a call can reach could not be determined | miss, wrong edge | Which macro the call selects |
490
+ | `unsupported_jinja_construct` | A Jinja construct the analysis does not model | miss, wrong edge | That part of the template |
491
+ | `jinja_render_failed` | The template could not be interpreted | miss, wrong edge | The template syntax |
492
+ | `analysis_limit_reached` | The analysis stopped at a recursion or work limit | miss, wrong edge | Deeply recursive macros |
493
+ | `unsupported_ref_package` | A `ref()` naming a package, resolved by name only | miss, wrong edge | That the edge goes to the intended node |
494
+ | `ambiguous_ref` | A `ref()` matching several nodes (`candidates`); the edge goes to one of them | miss, wrong edge | Rename one of them |
495
+ | `not_assessed` | The node's dependencies are not assessed at all (`scope`: `manifest_dependencies`, `semantic_dependencies`, or `phantom_dependencies` on phantom nodes, which is never a gap) | anything | |
496
+
497
+ A reason does not establish that an edge is wrong or that one is missing. Literal `ref()` calls under a condition dlin cannot evaluate still produce edges, so `impacted_nodes` may include nodes that are not affected.
498
+
499
+ A skipped input (`input_skipped`: a file that could not be listed, read or parsed) belongs to no node. Besides the dependencies it holds, it can change how names and macros resolve elsewhere, so it is a gap of every exploration that ran.
500
+
416
501
  ## Filtering
417
502
 
418
503
  ```sh
@@ -92,7 +92,7 @@ For model-name inputs, `manifest.json` is the only file needed in manifest mode.
92
92
  - `var()` resolves from `vars.yml` or `dbt_project.yml`, then its default (`--vars` CLI overrides not supported)
93
93
  - `env_var()` uses its default and never reads the environment. A different value at run time can select a different dependency or branch than the one shown
94
94
  - Values known only at run time (`target`, `env_var()` without a default, `run_query()` results) do not select dependencies; `execute` is false, as when dbt parses the project
95
- - Dependencies selected through `adapter.dispatch()` or namespaced package macros (e.g. `dbt_utils.*`) may be missed
95
+ - Dependencies selected through `adapter.dispatch()` or namespaced package macros (e.g. `dbt_utils.*`) may be missed. The nodes concerned are reported as partial (see [Completeness of model-level dependencies](#completeness-of-model-level-dependencies))
96
96
  - Generic test IDs are dlin-specific (e.g. `test.not_null.orders.order_id`) and do not match dbt's naming; use manifest mode when exact test IDs matter
97
97
 
98
98
  When these limitations matter, use `--source manifest`.
@@ -134,7 +134,7 @@ For analysts and agents who work from a distributed `manifest.json` without acce
134
134
  dlin mcp --manifest-path path/to/manifest.json
135
135
  ```
136
136
 
137
- Available MCP tools: project summary, model search, lineage, impact analysis, and column-level lineage.
137
+ Tools return compact JSON as a single text result. Use `get_project_summary` to check manifest freshness and loading diagnostics. Lineage and impact results distinguish confirmed paths from possible paths and show where analysis could not continue. Request `detail: "full"` for paths and evidence, or follow `page.next_cursor` with the same query for more rows. Use `include_sql: true` with `find_nodes` to request compiled SQL.
138
138
 
139
139
  The SQL dialect for column lineage is detected from the manifest's `adapter_type`; `--dialect` overrides it. Requires a compiled `manifest.json` (`dbt compile`).
140
140
 
@@ -315,9 +315,9 @@ dlin column upstream customers --column order_count --column lifetime_value -o p
315
315
 
316
316
  ```
317
317
  customers (2 columns listed: 2 complete, 0 partial)
318
- order_count → orders.id → stg_orders.order_id → orders.order_id (aggregation)
318
+ order_count → raw.orders.id → stg_orders.order_id → orders.order_id (aggregation)
319
319
  boundary: external relation at stg_orders.order_id for customers.order_count: raw.orders (source, policy: snapshot unsupported; seed external)
320
- lifetime_value → payments.amount → stg_payments.amount → orders.total_amount (aggregation)
320
+ lifetime_value → raw.payments.amount → stg_payments.amount → orders.total_amount (aggregation)
321
321
  boundary: external relation at stg_payments.amount for customers.lifetime_value: raw.payments (source, policy: snapshot unsupported; seed external)
322
322
  assumes yaml:source.clp.raw.orders (YAML columns taken as exhaustive): order_count
323
323
  assumes yaml:source.clp.raw.payments (YAML columns taken as exhaustive): lifetime_value
@@ -413,6 +413,91 @@ Impacted Nodes:
413
413
  [low ] assert_orders_positive_amount (test, distance: 1)
414
414
  ```
415
415
 
416
+ ### Completeness of model-level dependencies
417
+
418
+ dlin reports where it could not analyse the model-level dependencies (`ref()`, `source()`, tests, exposures), so a program can tell whether a result may be missing something.
419
+
420
+ - **Each node** has `dependency_analysis` in `list` JSON (by default), in `graph` JSON (with `--json-full` or `--json-fields dependency_analysis`) and in `impact` JSON. Its `status` is `complete` or `partial`; `unresolved` lists a typed reason for each part that could not be analysed. `complete` means that, under dlin's evaluation rules, no part was left unresolved. In particular, `env_var()` is evaluated with its default, so a different value at run time can select another dependency; check run-time dependencies with a manifest generated for that environment.
421
+ - **Each impact report** has `exploration`, which says whether the reached nodes can be missing a node. It is `complete` only when no node outside the reached set has reasons (phantom nodes, which stand for unresolved targets, are left out; the nodes referencing them carry the reasons), no input was skipped and no scope went unassessed. Otherwise `gaps` lists why. An empty `exploration` means the search did not run, as for an input that is an unresolved reference. Manifest mode takes the manifest's dependencies as they are, so its exploration is always incomplete with `not_assessed` (`manifest_dependencies`).
422
+ - `complete` concerns the reached set only. It does not confirm that each reached node is affected, nor the distances or paths. It is relative to the project and the paths it configures: a configured path that does not exist is a warning, not a gap.
423
+ - A node whose analysis is `complete` says nothing about the project as a whole: an input that could not be read is not attributed to any node. Do not conclude that a project is fully analysed because every listed node is `complete`.
424
+ - A reason states that something was not analysed, not that a dependency is missing.
425
+
426
+ On stderr, a command that builds the graph prints, once and before any filtering:
427
+
428
+ - at most one configuration warning, such as a path in `dbt_project.yml` that does not exist;
429
+ - one `dependency_analysis_summary` when any node has reasons or any project gap remains. It counts the whole project: `partial_nodes` (as in node JSON), `not_assessed_nodes` (the partial nodes whose only reasons are `not_assessed`), reasons by type and namespace, and project gaps. It is a warning when a node is partially analysed or an input was skipped, and info when only scopes are not assessed, as in manifest mode. It is not the exploration of any impact report.
430
+
431
+ `--verbose` adds one diagnostic per reason, with its node and call site, one per project gap, and the info diagnostics for default paths that do not exist. `--quiet` suppresses all of them. With `--error-format json`, these diagnostics carry a `code` and typed fields next to `level`, `what`, `why` and `hint`; read the code and the fields, not the text.
432
+
433
+ #### Using impact in CI
434
+
435
+ To accept "no impact" only when it is proved, check every condition, not only an empty `impacted_nodes`. The first definition rejects an exploration whose `status` and `gaps` disagree:
436
+
437
+ ```sh
438
+ dlin impact orders -o json -q > impact.json && jq -e --arg id model.orders '
439
+ def consistent:
440
+ (.gaps | type == "array")
441
+ and ((.status == "complete" and (.gaps | length == 0))
442
+ or (.status == "incomplete" and (.gaps | length > 0)));
443
+ def model_explorations: [.exploration[] | select(.kind == "model_dependency")];
444
+ length == 1
445
+ and (.[0] | .source_node.unique_id == $id
446
+ and (.impacted_nodes | type == "array" and length == 0)
447
+ and (model_explorations | length > 0
448
+ and all(.[]; consistent and .status == "complete")))
449
+ ' impact.json
450
+ ```
451
+
452
+ Checking `source_node.unique_id` catches an input that did not resolve to the node you meant; with several inputs, check each report. `impact` succeeds as long as one input is found, and its exit code does not depend on completeness.
453
+
454
+ You may decide, after checking them, that some reasons do not hide a dependency in your project. To proceed despite them, accept a gap only when every one of its reasons matches a rule you have checked, and reject everything else, including reason and gap types you do not know. For example, to accept calls through the `dbt` namespace:
455
+
456
+ ```sh
457
+ jq -e --arg id model.orders '
458
+ def consistent:
459
+ (.gaps | type == "array")
460
+ and ((.status == "complete" and (.gaps | length == 0))
461
+ or (.status == "incomplete" and (.gaps | length > 0)));
462
+ def accepted:
463
+ .type == "unresolved_dependencies"
464
+ and (.reasons | type == "array" and length > 0)
465
+ and all(.reasons[]; .type == "unsupported_macro_namespace" and .namespace == "dbt");
466
+ def model_explorations: [.exploration[] | select(.kind == "model_dependency")];
467
+ length == 1
468
+ and (.[0] | .source_node.unique_id == $id
469
+ and (model_explorations | length > 0
470
+ and all(.[]; consistent and all(.gaps[]; accepted))))
471
+ ' impact.json
472
+ ```
473
+
474
+ Accepting gaps is a decision to take the risk; it does not prove that the change has no impact. The `namespace` is the name written in the call, not the package that owns the macro, so a namespace alone does not make a call safe. Before accepting a rule, check that the macro and the macros it calls read no `ref()` or `source()`, and that no argument, branch or dispatch inside them selects a dependency.
475
+
476
+ In the table, *miss* means the graph may lack a dependency, and *wrong edge* that an edge dlin kept may not be the one dbt uses.
477
+
478
+ | Reason `type` | Meaning | May | Check |
479
+ | --- | --- | --- | --- |
480
+ | `unresolved_ref`, `unresolved_source` | The target could not be resolved in the searched paths | miss | The name, or that its file is in a searched path |
481
+ | `invalid_dependency_call` | `ref()` or `source()` with arguments that are not valid | miss | The call |
482
+ | `generic_test_body_not_analyzed` | The body of a generic test macro is not analysed; its YAML arguments are evaluated, and may carry reasons of their own | miss | Whether the test macro reads other models |
483
+ | `unsupported_dependency_expression`, `dependency_target_missing` | An exposure `depends_on` entry that is not supported or names nothing | miss | The entry |
484
+ | `unresolved_var` | A `var()` without a value or default selects a dependency | miss, wrong edge | Set the variable or give a default |
485
+ | `runtime_value_unknown` | A value known only when dbt runs (`target`, `env_var()` without a default, `run_query()`, ...) selects a dependency | miss, wrong edge | A manifest generated for that environment |
486
+ | `unsupported_dispatch` | `adapter.dispatch()` is not resolved | miss, wrong edge | The dispatched implementations |
487
+ | `unsupported_macro_namespace` | A macro called through a namespace (`dbt_utils.star()`, `dbt.type_string()`) is not analysed | miss, wrong edge | That macro, as described above |
488
+ | `unresolved_call` | A call whose callee could not be identified | miss, wrong edge | That the macro is defined in a searched path |
489
+ | `macro_reachability_unknown` | The macros a call can reach could not be determined | miss, wrong edge | Which macro the call selects |
490
+ | `unsupported_jinja_construct` | A Jinja construct the analysis does not model | miss, wrong edge | That part of the template |
491
+ | `jinja_render_failed` | The template could not be interpreted | miss, wrong edge | The template syntax |
492
+ | `analysis_limit_reached` | The analysis stopped at a recursion or work limit | miss, wrong edge | Deeply recursive macros |
493
+ | `unsupported_ref_package` | A `ref()` naming a package, resolved by name only | miss, wrong edge | That the edge goes to the intended node |
494
+ | `ambiguous_ref` | A `ref()` matching several nodes (`candidates`); the edge goes to one of them | miss, wrong edge | Rename one of them |
495
+ | `not_assessed` | The node's dependencies are not assessed at all (`scope`: `manifest_dependencies`, `semantic_dependencies`, or `phantom_dependencies` on phantom nodes, which is never a gap) | anything | |
496
+
497
+ A reason does not establish that an edge is wrong or that one is missing. Literal `ref()` calls under a condition dlin cannot evaluate still produce edges, so `impacted_nodes` may include nodes that are not affected.
498
+
499
+ A skipped input (`input_skipped`: a file that could not be listed, read or parsed) belongs to no node. Besides the dependencies it holds, it can change how names and macros resolve elsewhere, so it is a gap of every exploration that ran.
500
+
416
501
  ## Filtering
417
502
 
418
503
  ```sh
@@ -25,6 +25,25 @@ Finds all downstream dependents and assigns severity levels:
25
25
  Text output: human-readable report with severity and distance (degree).
26
26
  JSON output: structured array of impact reports for CI/programmatic use.
27
27
 
28
+ Completeness:
29
+ impacted_nodes are the nodes reached through the edges dlin found. They
30
+ may include nodes reached through an edge that is only a guess, and they
31
+ can miss nodes whose dependencies dlin could not analyse.
32
+ exploration says whether the reached set can miss a node:
33
+ complete no gap: no node outside the reached set may depend on it
34
+ incomplete gaps lists why it may: a node outside the reached set
35
+ whose dependencies are partial (unresolved_dependencies,
36
+ with the node's reasons), an input skipped while reading
37
+ the project (input_skipped), or a scope not assessed at
38
+ all (not_assessed, e.g. manifest_dependencies: manifest
39
+ mode takes the manifest's dependencies as they are)
40
+ An input that is an unresolved reference has an empty exploration.
41
+ source_node and each impacted node carry their own dependency_analysis.
42
+ The report proves that nothing is affected only when impacted_nodes is
43
+ empty and every exploration is complete with no gaps. Do not read an
44
+ empty impacted_nodes alone as \"no impact\". The exit code does not
45
+ depend on completeness.
46
+
28
47
  Stdin/pipe support:
29
48
  Accepts model names or file paths on stdin (one per line). \
30
49
  File paths (detected by extension or path separator) are resolved to model names \
@@ -76,9 +76,10 @@ Error format (--error-format):
76
76
  Error: <what>
77
77
  Why: <why> (when available)
78
78
  Hint: <hint> (when available)
79
- json Structured JSON on stderr (fixed schema):
79
+ json One JSON object per diagnostic on stderr, with at least
80
80
  {\"level\":\"error\",\"what\":\"...\",\"why\":...,\"hint\":...}
81
- why and hint are strings or null.
81
+ why and hint are strings or null. Typed diagnostics add
82
+ a \"code\" and fields of their own.
82
83
  Also settable via DLIN_ERROR_FORMAT=json",
83
84
  after_long_help = "\
84
85
  Examples:
@@ -109,12 +110,31 @@ pub struct Cli {
109
110
  long_help = "\
110
111
  Error/warning output format on stderr: text (default) or json.
111
112
 
112
- When json, diagnostics are emitted as structured JSON objects with a
113
- fixed schema: {\"level\":\"error\"|\"warning\",\"what\":\"...\",\"why\":...,\"hint\":...}
114
- where why and hint are either strings or null."
113
+ When json, each diagnostic is one JSON object on its own line. Every
114
+ object has {\"level\":\"error\"|\"warning\"|\"info\",\"what\":\"...\",\"why\":...,\"hint\":...},
115
+ where why and hint are either strings or null. Typed diagnostics add a
116
+ \"code\" and fields of their own; for example dependency_analysis_summary
117
+ adds counts by reason type and namespace. Read code and the typed fields,
118
+ not the text of what, why and hint."
115
119
  )]
116
120
  pub error_format: ErrorFormat,
117
121
 
122
+ /// Show each reason of the dependency analysis on stderr
123
+ #[arg(
124
+ long,
125
+ global = true,
126
+ long_help = "\
127
+ Show the details of the model dependency analysis on stderr.
128
+
129
+ By default, a command that builds the lineage graph prints at most one
130
+ configuration warning and one dependency_analysis_summary diagnostic, which
131
+ counts the reasons of the whole project by type and namespace. With
132
+ --verbose it also prints one diagnostic per reason (with the node and the
133
+ call site) and per skipped input, and the info diagnostics for default
134
+ paths that do not exist. It changes no analysis. --quiet takes precedence."
135
+ )]
136
+ pub verbose: bool,
137
+
118
138
  #[command(subcommand)]
119
139
  pub command: Command,
120
140
  }
@@ -282,7 +282,8 @@ Only the specified fields are emitted; unspecified fields are omitted.
282
282
 
283
283
  Available fields:
284
284
  unique_id, label, node_type, file_path, description,
285
- materialization, tags, columns, sql_content, exposure
285
+ materialization, tags, columns, sql_content, exposure,
286
+ dependency_analysis
286
287
 
287
288
  Default (when neither --json-fields nor --json-full is given):
288
289
  unique_id, label, node_type, file_path
@@ -291,6 +292,11 @@ The exposure field is an object containing label, type, url, maturity,
291
292
  and owner; it is non-null only for exposure nodes and must be explicitly
292
293
  requested via --json-fields or --json-full.
293
294
 
295
+ dependency_analysis has a status, complete or partial, and unresolved,
296
+ a typed reason for each part of the node's own dependencies that could
297
+ not be analysed. It does not say whether the project as
298
+ a whole was analysed; see `dlin impact --help`.
299
+
294
300
  Note: sql_content reads raw SQL files on disk in sql mode, or
295
301
  compiled_code from manifest.json in manifest mode (requires prior
296
302
  `dbt compile`)."
@@ -246,15 +246,21 @@ Only the specified fields are emitted; unspecified fields are omitted.
246
246
 
247
247
  Available fields:
248
248
  unique_id, label, node_type, file_path, description,
249
- materialization, tags, columns, sql_content, exposure
249
+ materialization, tags, columns, sql_content, exposure,
250
+ dependency_analysis
250
251
 
251
252
  Default (when neither --json-fields nor --json-full is given):
252
- unique_id, label, node_type, file_path
253
+ unique_id, label, node_type, file_path, dependency_analysis
253
254
 
254
255
  The exposure field is an object containing label, type, url, maturity,
255
256
  and owner; it is non-null only for exposure nodes and must be explicitly
256
257
  requested via --json-fields or --json-full.
257
258
 
259
+ dependency_analysis has a status, complete or partial, and unresolved,
260
+ a typed reason for each part of the node's own dependencies that could
261
+ not be analysed. It does not say whether the project as
262
+ a whole was analysed; see `dlin impact --help`.
263
+
258
264
  Note: sql_content reads raw SQL files on disk in sql mode, or
259
265
  compiled_code from manifest.json in manifest mode (requires prior
260
266
  `dbt compile`)."
@@ -110,8 +110,10 @@ pub(crate) fn run_column_lineage_command(
110
110
  };
111
111
 
112
112
  let column_filter: Vec<&str> = columns.iter().map(|s| s.as_str()).collect();
113
+ let seeds = read_seed_schemas(&project_dir, &manifest);
113
114
  let mut analysis =
114
- graph::column_lineage::ColumnLineageAnalysis::new(&manifest, dialect, &mut cache);
115
+ graph::column_lineage::ColumnLineageAnalysis::new(&manifest, dialect, &mut cache)
116
+ .with_seed_schemas(&seeds);
115
117
 
116
118
  let reports: Vec<_> = models
117
119
  .iter()
@@ -213,8 +215,10 @@ pub(crate) fn run_column_impact_command(
213
215
  graph::column_lineage::ColumnLineageCache::load(&project_dir, cache_dir)
214
216
  };
215
217
 
218
+ let seeds = read_seed_schemas(&project_dir, &manifest);
216
219
  let mut analysis =
217
- graph::column_lineage::ColumnLineageAnalysis::new(&manifest, dialect, &mut cache);
220
+ graph::column_lineage::ColumnLineageAnalysis::new(&manifest, dialect, &mut cache)
221
+ .with_seed_schemas(&seeds);
218
222
 
219
223
  let reports: Vec<_> = columns
220
224
  .iter()