Hi everyone! The convention in dagster seems to be...
# announcements
b
Hi everyone! The convention in dagster seems to be to keep objects in files/modules named after what they are -
resources.py
,
solids.py
, and so on. Has anyone tried any different structures, perhaps splitting things up by domain, or data source instead? Are there any reasons why the former approach would be considered best? Thank you in advance 🙂
s
Hi Ben - I believe the setup we currently recommend is to have a
resources/
directory, with a module per resource and a
solids/
directory, with a module per solid. If you get to the point where these directories have too much in them, then it likely makes sense to have domain-specific subdirectories
b
That’s great - Thanks, Sandy!