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

Alias NodeRelation.schema_name to simply 'schema' #108

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

peterallenwebb
Copy link

Resolves #106

Description

Alias NodeRelation.schema_name to simply 'schema'

Checklist

@cla-bot cla-bot bot added the cla:yes label Jul 11, 2023
@github-actions
Copy link

Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see the contributing guide.

@peterallenwebb peterallenwebb requested review from QMalcolm, graciegoheen and a team as code owners April 2, 2024 20:49
Copy link
Collaborator

@QMalcolm QMalcolm left a comment

Choose a reason for hiding this comment

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

I'm somewhat skeptical of these changes. If they work though, amazing. We should get the conflicts resolved first and the actions reran. As it is currently, it looks like last July we had some test failures, but github has killed the logs on what those were.

@tlento
Copy link
Collaborator

tlento commented Apr 3, 2024

I was just going to say exactly what @QMalcolm said. I just can't reason about what this alias magic from Pydantic will do in practice and I don't feel up to another deep dive into the Pydantic 1.10 codebase at this point.

Unfortunately our CI integrations between this repo and its various dependencies are lacking so we might be in a situation where we have to merge -> deploy -> test -> roll back.

@tlento
Copy link
Collaborator

tlento commented Apr 3, 2024

Also, why are we making this change? I can't tell if the protocols need to be updated here, or if this is step 1 in a multi-step migration process that has to be merged and deployed in sequence in order to safely update the protocols, or what our final outcome is generally expected to be.

Copy link
Collaborator

@tlento tlento left a comment

Choose a reason for hiding this comment

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

For some reason this is sitting in my review queue taking up cognitive space even though I commented eralier. I'm requesting changes just to see if I can alter the GitHub state, so if everybody else agrees that this is in a position to move forward please do clear that block rather than waiting for me to update my review.

In the meantime, it seems like this needs an update and CI re-run. If you could also add some context to the PR description around why we're making this change that'd help me expedite any follow-ups as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Rename the 'schema_name' field on node_relation to simply 'schema'
3 participants