-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Improved schema_generator tool #13518
Conversation
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.
Good stuff, i think you need to add unit tests and re-instate the licence. I only did a quick eye-ball on the logic
@@ -1,27 +1,3 @@ | |||
# | |||
# MIT License |
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.
I dont think you can drop the licence
from .configure_catalog import configure_catalog | ||
|
||
|
||
def main(): |
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.
Any unit tests for the tool?
Thank you @dougpm for this great contribution! Our team will review it soon. |
Hi @dougpm let me know if I'm wrong:
So I'm under the impression that this tool can't be used to initially create schema files while starting a new connector project. Am I right? |
Hey @alafanechere You're right, to generate the catalog we need the schema files. These files can be empty json files, they just need to be there for the |
Hey @dougpm I pinged our Developer Experience team to get their opinion about this addition 😄 |
@dougpm it would help if you can add a bit more details in your documentation about the context in which this tool can be used in the connector development cycle. |
@alafanechere Added a Prerequisites section in the tool README file. |
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.
Generally looks good, thanks for adding docs! would also support having unit tests here but otherwise LGTM
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.
@dougpm how do you feel about adding unit tests?
@alafanechere Sure I'll do that! |
Hey @dougpm do you have the bandwidth to implement the unit tests soon? |
Hey @alafanechere yes, I'll do it this week, sorry for the delay. |
@alafanechere tests added! |
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.
Thank you for adding the tests. I played with the schema generator locally, I had to make minor changes to the installation process to make it work.
What
Improves the developer experience when using the schema generator tool.
How
Recommended reading order
🚨 User Impact 🚨
Are there any breaking changes? What is the end result perceived by the user? If yes, please merge this PR with the 🚨🚨 emoji so changelog authors can further highlight this if needed.
Pre-merge Checklist
Expand the relevant checklist and delete the others.
New Connector
Community member or Airbyter
airbyte_secret
./gradlew :airbyte-integrations:connectors:<name>:integrationTest
.README.md
bootstrap.md
. See description and examplesdocs/integrations/<source or destination>/<name>.md
including changelog. See changelog exampledocs/integrations/README.md
airbyte-integrations/builds.md
Airbyter
If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.
/test connector=connectors/<name>
command is passing/publish
command described hereUpdating a connector
Community member or Airbyter
airbyte_secret
./gradlew :airbyte-integrations:connectors:<name>:integrationTest
.README.md
bootstrap.md
. See description and examplesdocs/integrations/<source or destination>/<name>.md
including changelog. See changelog exampleAirbyter
If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.
/test connector=connectors/<name>
command is passing/publish
command described hereConnector Generator
-scaffold
in their name) have been updated with the latest scaffold by running./gradlew :airbyte-integrations:connector-templates:generator:testScaffoldTemplates
then checking in your changesTests
Unit
Put your unit tests output here.
Integration
Put your integration tests output here.
Acceptance
Put your acceptance tests output here.