Skip to content

feat: add source naming convention#394

Open
deepanshupal09-datazip wants to merge 2 commits into
stagingfrom
feat/add-source-name-convention
Open

feat: add source naming convention#394
deepanshupal09-datazip wants to merge 2 commits into
stagingfrom
feat/add-source-name-convention

Conversation

@deepanshupal09-datazip

@deepanshupal09-datazip deepanshupal09-datazip commented Jun 17, 2026

Copy link
Copy Markdown
Collaborator

Description

This PR adds Source Naming Convention feature to UI. It will only be visible after v0.7.7 in both bulk edit and single edit.

Fixes # (issue)

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

  • Scenario A : Tested in both new job creation and job edit, in both bulk edit and single edit, the attribute is being passed correctly
  • Scenario B : Tested the upgrade path, if someone upgrade from an old source version to new version, the attribute is being passed correctly.
  • Scenario C : Tested that feature is not available in incompatible versions (below v0.7.7 for now).

Screenshots or Recordings

Screenshot 2026-06-17 at 3 37 16 PM Screenshot 2026-06-17 at 3 37 49 PM

Related PR's (If Any):

@deepanshupal09-datazip deepanshupal09-datazip changed the base branch from master to staging June 17, 2026 10:11
Comment on lines +80 to +81
// TODO: update this version before final merge
export const MIN_SOURCE_NAMING_CONVENTION_VERSION = "v0.7.7"

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's not forget to do this before merge

return selectedStream.selected_columns!.columns.includes(columnName)
}

// Returns true if the source version supports the source naming convention feature.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
// Returns true if the source version supports the source naming convention feature.
// Returns true if the source version supports the `use_source_column_names` feature.

?

}

// Returns true if the source version supports the source naming convention feature.
export function supportsSourceNamingConvention(

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
export function supportsSourceNamingConvention(
export function isUseSourceColumnNamesSupported(

Comment on lines +45 to +46
When enabled, the source naming convention will be applied to
destination table names.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this correct description?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this text is taken from the PRD

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants