-
Notifications
You must be signed in to change notification settings - Fork 4.5k
connectors-insights: fix generation for non manifest connector #43430
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
connectors-insights: fix generation for non manifest connector #43430
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @alafanechere and the rest of your teammates on |
c52fe25
to
e15223d
Compare
e15223d
to
c7e9220
Compare
c7e9220
to
3ff6048
Compare
Oh noes, did I break it? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Dammit this is embarrasing. Thank you a lot for fixing this! TIL.
manifest = connector.manifest_path.read_text() | ||
|
||
schemas_directory = connector.code_path / connector.technical_name.replace("-", "_") / "schemas" | ||
schemas_directory = connector.code_directory / connector.technical_name.replace("-", "_") / "schemas" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wait up, did I mess it up and it never worked? How did I manage that without failing a test? Or does code_path
exist, but does a different thing? What's the difference between them?
Yes but that's the cost of not writing tests ahah |
What
Insights generation is broken:
Connector.code_path
attribute does not exists.Connector insights generation now works again.