-
Notifications
You must be signed in to change notification settings - Fork 388
feat: updated scaffolding template #3275
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
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
docs | b93a710 | Commit Preview URL Branch Preview URL |
Nov 12 2025, 10:04 PM |
rudolfix
left a comment
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.
LGTM, thx for fixing this
rudolfix
left a comment
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.
Note: I've modified AST parser to allow optional dataset names and script import checker to allow pipelines to be instantiated on import (makes sense also for runtime)
pipeline running, iterating resources and source instantiation is not allowed
|
Converted to draft to avoid merging. I realized that I think the |
e5c8f3a to
b93a710
Compare
This updates the template with several changes:
vibe codingand specifics about dlt commandsfrom dlt.sources.rest_api.typing. The previous import was unintended and creates linting errors with pylance (this throws off IDE agents like Cursor)dlt.secrets.valueworksget_data()function. This scope is unecessary and adds complexity if we intend to run this as a script.dataset_namekwarg. This simplifies the work of the LLM. Anyways, the name is derived from the pipeline name.dev_mode=True, this avoids schema migrations across runs.refresh="drop_sources"to avoid state conflicts as the agents does multiple iterations