feat: Adds Parser interface and JsonParser component to declarative framework

[pnilan]

What

• Adds new Parser interface
• Adds new JsonParser component which accepts str, bytes, or bytearray data and yields a dict object.
• Resolves feat(JsonParser) - Create new JsonParser component #164

Recommended Reviewing Order:

1. declarative_component_schema.yaml
2. parsers.py
3. model_to_component_factory.py
4. test_parsers.py

Summary by CodeRabbit

• New Features

  • Introduced a new JsonParser component for flexible data parsing.
  • Added functionality to create instances of JsonParser through the ModelToComponentFactory.

• Bug Fixes

  • Improved formatting and readability of various field definitions across multiple classes.

• Tests

  • Added tests for the JsonParser to validate its ability to parse JSON data in different formats.

• Documentation

  • Updated copyright notice in the test files.

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request introduces a new JsonParser component to the Airbyte CDK, enhancing the declarative components framework by allowing for parsing of JSON data from various formats. It includes the addition of several files, such as a new parser class and associated testing functionality. The changes maintain the overall structure of the existing codebase while improving the flexibility and functionality of data parsing options.

Changes

File Path	Change Summary
airbyte_cdk/sources/declarative/declarative_component_schema.yaml	Added new component definition for JsonParser.
airbyte_cdk/sources/declarative/decoders/parsers/__init__.py	Created new file to import Parser and JsonParser, defining the public API.
airbyte_cdk/sources/declarative/decoders/parsers/parsers.py	Introduced Parser abstract class and JsonParser class with parsing methods.
airbyte_cdk/sources/declarative/models/declarative_component_schema.py	Added JsonParser class and made minor formatting improvements to existing classes.
airbyte_cdk/sources/declarative/parsers/model_to_component_factory.py	Updated factory to include JsonParser and added create_json_parser method.
unit_tests/sources/declarative/decoders/parsers/__init__.py	Added copyright notice; no functional changes.
unit_tests/sources/declarative/decoders/parsers/test_parsers.py	Added tests for JsonParser to validate parsing functionality with various input formats.

Assessment against linked issues

Objective	Addressed	Explanation
Create JsonParser class (Issue #164)	✅
Implement Parser interface with parse method	✅

Possibly related PRs

• feat(airbyte-cdk): add gzipjson decoder #20: This PR introduces a GzipJsonDecoder and modifies the declarative_component_schema.yaml, indicating a related enhancement in parsing capabilities.

Suggested labels

enhancement

Suggested reviewers

• maxi297

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between ed9a5e7 and 254f877.

📒 Files selected for processing (7)

• airbyte_cdk/sources/declarative/declarative_component_schema.yaml (1 hunks)
• airbyte_cdk/sources/declarative/decoders/parsers/__init__.py (1 hunks)
• airbyte_cdk/sources/declarative/decoders/parsers/parsers.py (1 hunks)
• airbyte_cdk/sources/declarative/models/declarative_component_schema.py (10 hunks)
• airbyte_cdk/sources/declarative/parsers/model_to_component_factory.py (4 hunks)
• unit_tests/sources/declarative/decoders/parsers/__init__.py (1 hunks)
• unit_tests/sources/declarative/decoders/parsers/test_parsers.py (1 hunks)

✅ Files skipped from review due to trivial changes (2)

• unit_tests/sources/declarative/decoders/parsers/init.py
• airbyte_cdk/sources/declarative/decoders/parsers/init.py

👮 Files not reviewed due to content moderation or server errors (5)

• unit_tests/sources/declarative/decoders/parsers/test_parsers.py
• airbyte_cdk/sources/declarative/decoders/parsers/parsers.py
• airbyte_cdk/sources/declarative/models/declarative_component_schema.py
• airbyte_cdk/sources/declarative/parsers/model_to_component_factory.py
• airbyte_cdk/sources/declarative/declarative_component_schema.yaml

---

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:

‼️ IMPORTANT
Auto-reply has been disabled for this repository in the CodeRabbit settings. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

• 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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.
  • @coderabbitai help me debug CodeRabbit configuration file.

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 using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Experiment)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration 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.

[pnilan]

@coderabbitai

Are you able to provide a recommended reviewing order of the altered files?

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

@pnilan

Certainly! Here's a recommended order for reviewing the altered files:

1. airbyte_cdk/sources/declarative/decoders/parsers/parsers.py
   Start with this file as it introduces the new Parser interface and the JsonParser implementation. Understanding these classes is essential since they form the core of the new parsing functionality.

2. airbyte_cdk/sources/declarative/decoders/parsers/__init__.py
   Next, review the __init__.py file to see how the Parser and JsonParser are exposed for use elsewhere in the codebase.

3. airbyte_cdk/sources/declarative/parsers/model_to_component_factory.py
   Then, look at how the JsonParser is integrated into the ModelToComponentFactory. This will show you how instances of JsonParser are created and utilized within the framework.

4. airbyte_cdk/sources/declarative/models/declarative_component_schema.py
   Review the additions and modifications in this file to understand how the JsonParser is represented in the declarative model schema.

5. airbyte_cdk/sources/declarative/declarative_component_schema.yaml
   This YAML file defines the new JsonParser component in the schema, which is important for declarative configurations.

6. unit_tests/sources/declarative/decoders/parsers/test_parsers.py
   Finally, review the unit tests to verify that the JsonParser functions as expected and is properly tested.

7. unit_tests/sources/declarative/decoders/parsers/__init__.py
   The changes here are minimal, mainly adding the necessary imports for the new tests.

This order should help you build a clear understanding from the core implementation of the parser interface to how it's integrated into the existing framework, and finally to how it's tested. Wdyt?

[pnilan]

@coderabbitat

First off, you should ignore all __init__.py files when providing a recommended reviewing order. Additionally, for the context of this repo, you can always ignore including the declarative_component_schema.py file as this is auto-generated based on the declarative_component_schema.yaml file. Additionally, when providing a recommended reading order, it's fine to just include the filename and not the full path (unless there are multiple files with similar names).

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

@pnilan, thank you for the clarification! I'll make sure to exclude all __init__.py files and the declarative_component_schema.py file from the recommended reviewing order for this repository, since declarative_component_schema.py is auto-generated based on the declarative_component_schema.yaml file. Additionally, I'll include just the filenames without the full paths when providing the reading order unless there are multiple files with similar names. Let me know if there's anything else I can assist with!

---

✏️ Learnings added

Learnt from: pnilan
URL: https://github.com/airbytehq/airbyte-python-cdk/pull/166

Timestamp: 2024-12-11T16:34:46.122Z
Learning: In the airbytehq/airbyte-python-cdk repository, ignore all `__init__.py` files when providing a recommended reviewing order.

---

Learnt from: pnilan
URL: https://github.com/airbytehq/airbyte-python-cdk/pull/166

Timestamp: 2024-12-11T16:34:46.122Z
Learning: In the airbytehq/airbyte-python-cdk repository, the `declarative_component_schema.py` file is auto-generated from `declarative_component_schema.yaml` and should be ignored in the recommended reviewing order.

---

Learnt from: pnilan
URL: https://github.com/airbytehq/airbyte-python-cdk/pull/166

Timestamp: 2024-12-11T16:34:46.122Z
Learning: When providing a recommended reading order, include just the filenames without full paths unless there are multiple files with similar names.

Note: Learnings are effective only in the context of similar code segments. To apply general coding guidelines, please configure review instructions. You can manage existing learnings in the app.