Hey, just a heads up - I think there should be bet...
# dagster-feedback
m
Hey, just a heads up - I think there should be better documentation around how dagster defines and finds it's components in a project. I spent the last few hours working through scheduler definitions and sensors, but could not find them - I even got them to run without them appearing in the dagit UI. In the end it was because my init file from when I created the project in December was using:
Copy code
from .repository import my_dagster_project
and
repository.py
was:
Copy code
from dagster import load_assets_from_package_module, repository
from my_dagster_project import assets


@repository
def my_dagster_project():
    return [load_assets_from_package_module(assets)]
I changed that to
Copy code
from .repository import my_dagster_project
and
Copy code
from dagster import Definitions, load_assets_from_package_module
from my_dagster_project import assets



all_assets = load_assets_from_package_module(assets)

defs = Definitions(
    assets=all_assets,
    schedules=[assets.dg_test_schedule.update_job_schedule]
)
And now things work However, this took me far too long 😂 - it should have been flagged as a gotcha somewhere IMO