Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

For single-table use cases, make it frictionless to update Metadata #2228

Merged
merged 9 commits into from
Sep 18, 2024

Conversation

R-Palazzo
Copy link
Contributor

@R-Palazzo R-Palazzo commented Sep 16, 2024

Resolve #2213

@R-Palazzo R-Palazzo self-assigned this Sep 16, 2024
@R-Palazzo R-Palazzo requested a review from a team as a code owner September 16, 2024 14:29
@R-Palazzo R-Palazzo removed the request for review from a team September 16, 2024 14:29
Base automatically changed from issue-2215-validate_table to feature/metadata September 16, 2024 15:13
@R-Palazzo R-Palazzo force-pushed the issue-2213-frictionless-update-metadata branch from 4e62dbe to 2bccb96 Compare September 16, 2024 15:32
@@ -173,7 +173,7 @@ def set_sequence_index(self, table_name, column_name):
self._validate_table_exists(table_name)
self.tables[table_name].set_sequence_index(column_name)

def set_sequence_key(self, table_name, column_name):
def set_sequence_key(self, *args, **kwargs):
Copy link
Contributor

Choose a reason for hiding this comment

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

I think for all of these we can just use the signature normally. For this one it would be set_sequence_key(self, column_name, table_name). I don't think we have to support a different order

Comment on lines 258 to 259
parameters = self._resolve_arguments(['column_name'], *args, **kwargs)
super().update_column(**parameters)
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't think we need this. Can we just list the args normally and then pass them in the correct order when calling super?

Copy link
Contributor

@lajohn4747 lajohn4747 left a comment

Choose a reason for hiding this comment

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

lgtm

Copy link
Contributor

@amontanez24 amontanez24 left a comment

Choose a reason for hiding this comment

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

:shipit:

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.

3 participants