-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
[components][docs] Add components doc on moving definitions into components #27721
base: master
Are you sure you want to change the base?
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. |
Deploy preview for dagster-docs ready! Preview available at https://dagster-docs-ouwfj0qk6-elementl.vercel.app Direct link to changed pages: |
c88201e
to
eabb2ea
Compare
<CliInvocationExample path="docs_beta_snippets/docs_beta_snippets/guides/components/migrating-definitions/4-scaffold.txt" /> | ||
|
||
|
||
This creates a new folder in `my_existing_project/components/elt-definitions`, with a `component.yaml` file. This component is rather simple, it just points to a file which contains a `Definitions` object. |
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.
Replace 'simple' with more specific descriptive language like 'straightforward' or describe its single responsibility, as per style guide requirements
Spotted by Graphite Reviewer (based on CI logs)
Is this helpful? React 👍 or 👎 to let us know.
Summary
Adds some brief, tested docs which migrate existing definitions module into a component.
One snag I hit here is that relative imports are not possible in a component folder, so it becomes pretty tricky to migrate any submodule which has multiple files.
https://dagster-docs-eanwjgfbu-elementl.vercel.app/guides/preview/components/migrating-definitions
Test Plan
See rendered docs, new test.