Support dbt 1.8

[yu-iskw]

No description provided.

[coderabbitai]

Walkthrough

The recent updates to the dbt_artifacts_parser module introduce support for ManifestV12 and RunResultsV6 versions. These changes ensure compatibility with the latest DBT artifacts, enhancing the parser's functionality. Modifications span multiple files, including the addition of new classes, functions, and test cases to handle these new versions seamlessly.

Changes

File Path	Change Summary
dbt_artifacts_parser/parser.py	Added support for ManifestV12 and RunResultsV6 in parsing functions and introduced new parsing logic.
dbt_artifacts_parser/parsers/manifest/...	Added a blank line before ResourceType11 class definition in manifest_v11.py.
dbt_artifacts_parser/parsers/run_results/...	Introduced run_results_v6.py with data models for parsing DBT run results version 6.
dbt_artifacts_parser/parsers/version_map.py	Added imports and declarations for ManifestV12 and RunResultsV6 artifact types.
dev/generate_parser_classes.sh	Updated script to include "v12" and "v6" in the respective version arrays.
tests/test_parser.py	Added "v12" and "v6" to test data paths and parameterized versions in the TestRunResultsParser class.

🐇✨
In the world of code, we hop and play,
With ManifestV12, we found our way.
RunResultsV6 joins the dance,
Parsing data with a glance.
Tests and scripts, all aligned,
A rabbit's work, finely designed.
🌟📜

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 2

Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 2171854 and 9f1072d.

Files ignored due to path filters (4)

• dbt_artifacts_parser/resources/manifest/manifest_v12.json is excluded by !**/*.json
• dbt_artifacts_parser/resources/run-results/run-results_v6.json is excluded by !**/*.json
• tests/resources/v12/jaffle_shop/manifest.json is excluded by !**/*.json
• tests/resources/v6/jaffle_shop/run_results.json is excluded by !**/*.json

Files selected for processing (6)

• dbt_artifacts_parser/parser.py (6 hunks)
• dbt_artifacts_parser/parsers/manifest/manifest_v11.py (1 hunks)
• dbt_artifacts_parser/parsers/run_results/run_results_v6.py (1 hunks)
• dbt_artifacts_parser/parsers/version_map.py (2 hunks)
• dev/generate_parser_classes.sh (2 hunks)
• tests/test_parser.py (2 hunks)

Files skipped from review due to trivial changes (3)

• dbt_artifacts_parser/parsers/manifest/manifest_v11.py
• dev/generate_parser_classes.sh
• tests/test_parser.py

Additional comments not posted (4)

dbt_artifacts_parser/parsers/run_results/run_results_v6.py (1)

72-79: The structure and implementation of RunResultsV6 look good and are well-suited for the intended purpose.

dbt_artifacts_parser/parsers/version_map.py (1)

Line range hint 34-102: The updates to the version map to include ManifestV12 and RunResultsV6 are correctly implemented with appropriate schema URLs and class references.

dbt_artifacts_parser/parser.py (2)

31-37: The updated import statements to include ManifestV12 and RunResultsV6 are correctly implemented.

---

Line range hint 87-297: The updates to the parsing functions to handle ManifestV12 and RunResultsV6 are correctly implemented and ensure that the new versions are handled appropriately.

[coderabbitai]

Consider simplifying the use of multiple enums for status. If distinct statuses are necessary, ensure clear documentation or consider merging them into a single enum with additional states.

[coderabbitai]

Consider simplifying the type hint for invocation_id from Optional[Optional[str]] to Optional[str].