This repository was archived by the owner on Jan 20, 2026. It is now read-only.
feature/july-25-connector-update#21
Merged
fivetran-joemarkiewicz merged 5 commits intomainfrom Jul 14, 2025
Merged
Conversation
Contributor
fivetran-catfritz
left a comment
There was a problem hiding this comment.
Just some preliminary comments on the docs generator!
Co-authored-by: fivetran-catfritz <111930712+fivetran-catfritz@users.noreply.github.com>
Co-authored-by: fivetran-catfritz <111930712+fivetran-catfritz@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR Overview
Package version introduced in this PR: v0.4.0
This PR addresses the following Issue/Feature(s): Internal issue to comply with July 2025 connector updates
Summary of changes:
Introduced updates to ensure the Recharge data model is aligned with updates being applied to the Fivetran Recharge connector. Many updates were already addressed; however, the
_is_deleteddeprecation and_fivetran_deletedadditions were not accounted. This update focuses exclusively on those deprecation and additions. I made to sure have the_fivetran_deletedfield be included in cases where it's being used, and to not remove the_is_deletedfield but clearly identify the deprecation of it. This will allow for a smoother transition for some users. Also, it didn't seem that these fields were entirely 1:1 so I didn't want to perform a coalesce. It felt better to keep them separate and we will remove the_is_deletedin a future breaking change.Submission Checklist
Changelog