Thanks to visit codestin.com
Credit goes to github.com

Skip to content

refactor: Make outputs from value matching consistent with other methods#116

Merged
roquelopez merged 1 commit intodevelfrom
refactor_outputs_value_matching
Jun 17, 2025
Merged

refactor: Make outputs from value matching consistent with other methods#116
roquelopez merged 1 commit intodevelfrom
refactor_outputs_value_matching

Conversation

@roquelopez
Copy link
Collaborator

No description provided.

@roquelopez roquelopez force-pushed the refactor_outputs_value_matching branch from 8cfdb78 to 1eb1e96 Compare May 29, 2025 21:32
@review-notebook-app
Copy link

Check out this pull request on  ReviewNB

See visual diffs & provide feedback on Jupyter Notebooks.


Powered by ReviewNB

Comment on lines +12 to +13
source_attribute: str
target_attribute: str
Copy link
Member

Choose a reason for hiding this comment

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

Shall we use source_column and target_column instead? It is shorter, and it's what is being used as parameter names in the public API, and it is consistent with Pandas.

I also noticed that there is some new code internally using "attribute", so maybe we should converge to use a consistent nomenclature (but this could be a separate commit/PR).

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Thanks for the review! I had the same question about whether to use target_column or target_attribute. The main reason I opted for attribute is that in data models like GDC, the concept of columns doesn’t exist, and using column in that context could be somewhat confusing. I would vote to use attribute since it works well both in such cases and in table-to-table scenarios. Additionally, it seems that the term attribute is commonly used in schema matching. I’m also open to using column if that’s preferred.

And yes, my plan was to open a new PR to standardize the selected terminology in parts you mentioned.

What do you think @aecio?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

As discussed, we will merge this PR and keep the proposed changes.

@roquelopez roquelopez merged commit 24e4883 into devel Jun 17, 2025
14 checks passed
@roquelopez roquelopez deleted the refactor_outputs_value_matching branch June 17, 2025 14:07
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