-
Notifications
You must be signed in to change notification settings - Fork 3
Add MARIMO_FOLDER to deptry configuration variables #519
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
base: main
Are you sure you want to change the base?
Changes from all commits
1aa1596
a3625a4
e3d271f
f6d177d
0eae216
7d6bc84
e8318ea
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,15 @@ | ||
| ## Makefile.src - Source folder configuration | ||
| # This file is included by the main Makefile | ||
|
|
||
| # Add SOURCE_FOLDER to deptry configuration if it exists | ||
| ifneq ($(wildcard $(SOURCE_FOLDER)),) | ||
| DEPTRY_FOLDERS += $(SOURCE_FOLDER) | ||
| endif | ||
|
Comment on lines
+1
to
+7
|
||
|
|
||
| ##@ Quality and Formatting | ||
| deptry: install-uv ## Run deptry | ||
|
Comment on lines
+9
to
+10
|
||
| @printf "${BLUE}[INFO] DEPTRY_FOLDERS: ${DEPTRY_FOLDERS}${RESET}\n" | ||
| @if [ -n "$(strip ${DEPTRY_FOLDERS})" ]; then \ | ||
| printf "${BLUE}[INFO] Running: $(UVX_BIN) -p ${PYTHON_VERSION} deptry ${DEPTRY_FOLDERS} ${DEPTRY_IGNORE}${RESET}\n"; \ | ||
|
Comment on lines
+11
to
+13
|
||
| $(UVX_BIN) -p ${PYTHON_VERSION} deptry ${DEPTRY_FOLDERS} ${DEPTRY_IGNORE}; \ | ||
| fi | ||
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.
Consider renaming this file to follow the numeric prefix convention documented in .rhiza/make.d/README.md. Since this file defines a target (deptry) which is a quality checking tool, it could be numbered in the 20-79 range (e.g., "02-src.mk" or similar) for consistency with other target-defining files like 01-test.mk, 03-marimo.mk, etc.
However, if the intent is for this file to represent core/fundamental source folder configuration (without a prefix to indicate its foundational nature), then the current naming is acceptable.