dev-scaffolder 0.0.1__tar.gz

dev_scaffolder-0.0.1/LICENSE

@@ -0,0 +1,19 @@
+Copyright (c) 2018 The Python Packaging Authority
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

dev_scaffolder-0.0.1/PKG-INFO

@@ -0,0 +1,230 @@
+Metadata-Version: 2.4
+Name: dev-scaffolder
+Version: 0.0.1
+Summary: A dynamic, interactive CLI-based project generator with a tree-based question system and custom template executors.
+Author-email: Faisal Issaka <phaisalsey6@gmail.com>
+License-Expression: MIT AND (Apache-2.0 OR BSD-2-Clause)
+Project-URL: Homepage, https://github.com/Faisal-Sey/dev-scaffolder
+Project-URL: Issues, https://github.com/Faisal-Sey/dev-scaffolder/issues
+Keywords: scaffolder,cli,project-generator,templates
+Classifier: Development Status :: 4 - Beta
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.8
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Software Development :: Code Generators
+Requires-Python: >=3.8
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: ansicon==1.89.0
+Requires-Dist: blessed==1.33.0
+Requires-Dist: editor==1.7.0
+Requires-Dist: inquirer==3.4.1
+Requires-Dist: jinxed==1.3.0
+Requires-Dist: markdown-it-py==4.0.0
+Requires-Dist: mdurl==0.1.2
+Requires-Dist: Pygments==2.19.2
+Requires-Dist: python-dotenv==1.2.2
+Requires-Dist: readchar==4.2.1
+Requires-Dist: rich==14.3.3
+Requires-Dist: runs==1.3.0
+Requires-Dist: wcwidth==0.6.0
+Requires-Dist: xmod==1.9.0
+Dynamic: license-file
+
+# Project Scaffolder
+
+A dynamic, interactive CLI-based project generator that simplifies the process of scaffolding new projects through a tree-based question system and custom template executors.
+
+## Features
+
+- **Interactive Question Tree**: Navigate through a logical hierarchy of choices defined in JSON.
+- **Extensible Architecture**: Easily add new templates and questions by adding JSON files and Python executors.
+- **Styled CLI Output**: Uses `rich` to provide a clean and professional command-line interface with panels, colors, and spinners.
+- **Robust Input Handling**: Powered by `inquirer` for intuitive selections and confirmations.
+- **Environment-Aware Output**: Projects and virtual environments are created in `temp/` during development, keeping generated files out of version control.
+- **Base Executor Pattern**: All executors inherit from `BaseExecutor`, which provides a consistent lifecycle and a built-in loading spinner that automatically pauses around interactive prompts.
+
+## Installation
+
+### Prerequisites
+
+- Python 3.8+
+
+### Setup
+
+1. Clone the repository:
+   ```bash
+   git clone <repository-url>
+   cd template
+   ```
+
+2. Install the required dependencies:
+   ```bash
+   pip install -r requirements.txt
+   ```
+
+3. Configure your environment by creating a `.env` file in the project root:
+   ```env
+   ENVIRONMENT=development
+   ```
+   Accepted values: `development`, `production`.
+
+## Usage
+
+To start the project generation process, run the main scaffolder script:
+
+```bash
+python scripts/scaffolder/scaffolder.py
+```
+
+Follow the on-screen prompts to select your project type, language, and other configurations.
+
+## Project Structure
+
+```
+template/
+├── .env                   # Environment configuration (ENVIRONMENT=development|production)
+├── questions/             # JSON files defining the question hierarchy
+├── executors/             # Executor classes for each supported framework
+│   ├── base.py            # BaseExecutor abstract class (lifecycle + spinner)
+│   └── backend/
+│       └── python/
+│           └── django/    # Django-specific executors
+├── processors/            # Core logic: question loading, input handling, template resolution
+├── utils/
+│   ├── base.py            # Subprocess, file, and venv utilities
+│   └── env.py             # Environment detection and path resolution
+├── constants/             # Framework-specific code snippets and configuration strings
+├── typings/               # Shared type definitions and dataclasses
+└── scripts/               # Entry points for running the scaffolder
+```
+
+## How It Works
+
+1. **Question Loading**: The system starts by loading `questions/base.json`.
+2. **Dynamic Traversal**: Based on user selection, it recursively loads child questions from the file system.
+3. **Template Resolution**: Once a leaf node (a final choice) is reached, the system identifies the corresponding executor in the `executors/` directory.
+4. **Execution**: The executor's `run()` method is called with the gathered parameters. It starts a loading spinner, delegates to `generate()`, and stops the spinner when done.
+
+## Environment Modes
+
+The `ENVIRONMENT` variable in `.env` controls where generated output is placed.
+
+| `ENVIRONMENT` | Project output | Virtual environment |
+|---|---|---|
+| `development` | `<project_root>/temp/` | `<project_root>/temp/venv/` |
+| `production` | Current working directory | `<project_root>/venv/` |
+
+The `temp/` directory is listed in `.gitignore` so development output is never committed.
+
+## Executor Architecture
+
+All executors inherit from `BaseExecutor` (`executors/base.py`) and must implement:
+
+| Method | Purpose |
+|---|---|
+| `get_venv_environment()` | Set up and return the venv Python path |
+| `install_dependencies(venv_python_executor)` | Install framework packages |
+| `execute_creation_commands(**kwargs)` | Orchestrate the full scaffold |
+| `generate(**kwargs)` | Resolve arguments and drive the above steps |
+
+`prepare_directory()` is provided as a concrete default on `BaseExecutor` — it creates the output directory or prompts the user to replace it if one already exists. Override it only if the executor needs different behaviour.
+
+The public entry point is `run(**kwargs)`, which wraps `generate()` with a `rich` loading spinner. Use `self._stop_status()` / `self._start_status()` around any interactive `inquirer` prompts inside your executor to prevent the spinner from blocking user input. Use `self._update_status(message)` to update the spinner label as execution progresses through steps.
+
+### Adding a New Executor
+
+1. Create a JSON file in `questions/` defining the configuration options for the new template.
+2. Link it to the existing question tree via `questions/base.json`.
+3. Create a Python file in the corresponding `executors/` path and subclass `BaseExecutor`:
+
+```python
+from src.executors.base import BaseExecutor
+from typings.base import ExecutorResponseStatus
+
+
+class MyFrameworkExecutor(BaseExecutor):
+
+    def get_venv_environment(self) -> str:
+        ...
+
+    def install_dependencies(self, venv_python_executor: str) -> ExecutorResponseStatus:
+        ...
+
+    def execute_creation_commands(self, **kwargs) -> ExecutorResponseStatus:
+        ...
+
+    def generate(self, **kwargs):
+        ...
+
+
+if __name__ == '__main__':
+    args = MyFrameworkExecutor.build_arg_parser().parse_args()
+    MyFrameworkExecutor().run(**vars(args))
+```
+
+## Contributing
+
+### Branching
+
+- `main` — stable branch; only merge via pull request
+- Feature branches should follow the pattern: `feature/<short-description>` (e.g. `feature/fastapi-executor`)
+- Bug fix branches: `fix/<short-description>` (e.g. `fix/venv-path-dev-mode`)
+
+### Workflow
+
+1. Fork or branch from `main`:
+   ```bash
+   git checkout -b feature/<short-description>
+   ```
+
+2. Set up your environment:
+   ```bash
+   pip install -r requirements.txt
+   cp .env.example .env   # set ENVIRONMENT=development
+   ```
+
+3. Make your changes following the conventions below, then commit:
+   ```bash
+   git add <files>
+   git commit -m "feat: short description of change"
+   ```
+
+4. Push and open a pull request against `main`.
+
+### Adding a Question
+
+Questions live in `questions/` as JSON files and mirror the `executors/` directory structure. Each file defines a node in the question tree:
+
+```json
+{
+  "type": "list",
+  "name": "my_option",
+  "message": "Choose an option",
+  "choices": ["Option A", "Option B"],
+  "children": []
+}
+```
+
+Leaf nodes (no children) trigger executor resolution — the scaffolder maps the answer path directly to a file in `executors/`.
+
+### Adding an Executor
+
+Follow the steps in [Adding a New Executor](#adding-a-new-executor) above. Additional conventions:
+
+- Place the file at `executors/<category>/<language>/<framework>/<name>.py` to match the question path.
+- Use `self.console` for all terminal output — never use `print()`.
+- Use `self._update_status(message)` to label each distinct step in `execute_creation_commands`.
+- Call `self._stop_status()` before any `inquirer.prompt()` and `self._start_status()` immediately after.
+- All subprocess calls must use the venv Python executor (`get_venv_python_executor()`) rather than bare shell commands, so they work correctly in both `development` and `production` environments.
+
+### Code Style
+
+- Follow PEP 8.
+- All public methods must have docstrings with `:param:` and `:return:` annotations.
+- Keep `utils/` functions generic and stateless — executor-specific logic belongs in the executor class.

dev_scaffolder-0.0.1/README.md

@@ -0,0 +1,192 @@
+# Project Scaffolder
+
+A dynamic, interactive CLI-based project generator that simplifies the process of scaffolding new projects through a tree-based question system and custom template executors.
+
+## Features
+
+- **Interactive Question Tree**: Navigate through a logical hierarchy of choices defined in JSON.
+- **Extensible Architecture**: Easily add new templates and questions by adding JSON files and Python executors.
+- **Styled CLI Output**: Uses `rich` to provide a clean and professional command-line interface with panels, colors, and spinners.
+- **Robust Input Handling**: Powered by `inquirer` for intuitive selections and confirmations.
+- **Environment-Aware Output**: Projects and virtual environments are created in `temp/` during development, keeping generated files out of version control.
+- **Base Executor Pattern**: All executors inherit from `BaseExecutor`, which provides a consistent lifecycle and a built-in loading spinner that automatically pauses around interactive prompts.
+
+## Installation
+
+### Prerequisites
+
+- Python 3.8+
+
+### Setup
+
+1. Clone the repository:
+   ```bash
+   git clone <repository-url>
+   cd template
+   ```
+
+2. Install the required dependencies:
+   ```bash
+   pip install -r requirements.txt
+   ```
+
+3. Configure your environment by creating a `.env` file in the project root:
+   ```env
+   ENVIRONMENT=development
+   ```
+   Accepted values: `development`, `production`.
+
+## Usage
+
+To start the project generation process, run the main scaffolder script:
+
+```bash
+python scripts/scaffolder/scaffolder.py
+```
+
+Follow the on-screen prompts to select your project type, language, and other configurations.
+
+## Project Structure
+
+```
+template/
+├── .env                   # Environment configuration (ENVIRONMENT=development|production)
+├── questions/             # JSON files defining the question hierarchy
+├── executors/             # Executor classes for each supported framework
+│   ├── base.py            # BaseExecutor abstract class (lifecycle + spinner)
+│   └── backend/
+│       └── python/
+│           └── django/    # Django-specific executors
+├── processors/            # Core logic: question loading, input handling, template resolution
+├── utils/
+│   ├── base.py            # Subprocess, file, and venv utilities
+│   └── env.py             # Environment detection and path resolution
+├── constants/             # Framework-specific code snippets and configuration strings
+├── typings/               # Shared type definitions and dataclasses
+└── scripts/               # Entry points for running the scaffolder
+```
+
+## How It Works
+
+1. **Question Loading**: The system starts by loading `questions/base.json`.
+2. **Dynamic Traversal**: Based on user selection, it recursively loads child questions from the file system.
+3. **Template Resolution**: Once a leaf node (a final choice) is reached, the system identifies the corresponding executor in the `executors/` directory.
+4. **Execution**: The executor's `run()` method is called with the gathered parameters. It starts a loading spinner, delegates to `generate()`, and stops the spinner when done.
+
+## Environment Modes
+
+The `ENVIRONMENT` variable in `.env` controls where generated output is placed.
+
+| `ENVIRONMENT` | Project output | Virtual environment |
+|---|---|---|
+| `development` | `<project_root>/temp/` | `<project_root>/temp/venv/` |
+| `production` | Current working directory | `<project_root>/venv/` |
+
+The `temp/` directory is listed in `.gitignore` so development output is never committed.
+
+## Executor Architecture
+
+All executors inherit from `BaseExecutor` (`executors/base.py`) and must implement:
+
+| Method | Purpose |
+|---|---|
+| `get_venv_environment()` | Set up and return the venv Python path |
+| `install_dependencies(venv_python_executor)` | Install framework packages |
+| `execute_creation_commands(**kwargs)` | Orchestrate the full scaffold |
+| `generate(**kwargs)` | Resolve arguments and drive the above steps |
+
+`prepare_directory()` is provided as a concrete default on `BaseExecutor` — it creates the output directory or prompts the user to replace it if one already exists. Override it only if the executor needs different behaviour.
+
+The public entry point is `run(**kwargs)`, which wraps `generate()` with a `rich` loading spinner. Use `self._stop_status()` / `self._start_status()` around any interactive `inquirer` prompts inside your executor to prevent the spinner from blocking user input. Use `self._update_status(message)` to update the spinner label as execution progresses through steps.
+
+### Adding a New Executor
+
+1. Create a JSON file in `questions/` defining the configuration options for the new template.
+2. Link it to the existing question tree via `questions/base.json`.
+3. Create a Python file in the corresponding `executors/` path and subclass `BaseExecutor`:
+
+```python
+from src.executors.base import BaseExecutor
+from typings.base import ExecutorResponseStatus
+
+
+class MyFrameworkExecutor(BaseExecutor):
+
+    def get_venv_environment(self) -> str:
+        ...
+
+    def install_dependencies(self, venv_python_executor: str) -> ExecutorResponseStatus:
+        ...
+
+    def execute_creation_commands(self, **kwargs) -> ExecutorResponseStatus:
+        ...
+
+    def generate(self, **kwargs):
+        ...
+
+
+if __name__ == '__main__':
+    args = MyFrameworkExecutor.build_arg_parser().parse_args()
+    MyFrameworkExecutor().run(**vars(args))
+```
+
+## Contributing
+
+### Branching
+
+- `main` — stable branch; only merge via pull request
+- Feature branches should follow the pattern: `feature/<short-description>` (e.g. `feature/fastapi-executor`)
+- Bug fix branches: `fix/<short-description>` (e.g. `fix/venv-path-dev-mode`)
+
+### Workflow
+
+1. Fork or branch from `main`:
+   ```bash
+   git checkout -b feature/<short-description>
+   ```
+
+2. Set up your environment:
+   ```bash
+   pip install -r requirements.txt
+   cp .env.example .env   # set ENVIRONMENT=development
+   ```
+
+3. Make your changes following the conventions below, then commit:
+   ```bash
+   git add <files>
+   git commit -m "feat: short description of change"
+   ```
+
+4. Push and open a pull request against `main`.
+
+### Adding a Question
+
+Questions live in `questions/` as JSON files and mirror the `executors/` directory structure. Each file defines a node in the question tree:
+
+```json
+{
+  "type": "list",
+  "name": "my_option",
+  "message": "Choose an option",
+  "choices": ["Option A", "Option B"],
+  "children": []
+}
+```
+
+Leaf nodes (no children) trigger executor resolution — the scaffolder maps the answer path directly to a file in `executors/`.
+
+### Adding an Executor
+
+Follow the steps in [Adding a New Executor](#adding-a-new-executor) above. Additional conventions:
+
+- Place the file at `executors/<category>/<language>/<framework>/<name>.py` to match the question path.
+- Use `self.console` for all terminal output — never use `print()`.
+- Use `self._update_status(message)` to label each distinct step in `execute_creation_commands`.
+- Call `self._stop_status()` before any `inquirer.prompt()` and `self._start_status()` immediately after.
+- All subprocess calls must use the venv Python executor (`get_venv_python_executor()`) rather than bare shell commands, so they work correctly in both `development` and `production` environments.
+
+### Code Style
+
+- Follow PEP 8.
+- All public methods must have docstrings with `:param:` and `:return:` annotations.
+- Keep `utils/` functions generic and stateless — executor-specific logic belongs in the executor class.

dev_scaffolder-0.0.1/pyproject.toml

@@ -0,0 +1,74 @@
+[build-system]
+requires = ["setuptools >= 77.0.3"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "dev-scaffolder"
+version = "0.0.1"
+description = "A dynamic, interactive CLI-based project generator with a tree-based question system and custom template executors."
+readme = "README.md"
+authors = [
+    { name = "Faisal Issaka", email = "phaisalsey6@gmail.com" }
+]
+requires-python = ">=3.8"
+license = "MIT AND (Apache-2.0 OR BSD-2-Clause)"
+keywords = ["scaffolder", "cli", "project-generator", "templates"]
+classifiers = [
+    "Development Status :: 4 - Beta",
+    "Environment :: Console",
+    "Intended Audience :: Developers",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.8",
+    "Programming Language :: Python :: 3.9",
+    "Programming Language :: Python :: 3.10",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Topic :: Software Development :: Code Generators",
+]
+
+dependencies = [
+    "ansicon==1.89.0",
+    "blessed==1.33.0",
+    "editor==1.7.0",
+    "inquirer==3.4.1",
+    "jinxed==1.3.0",
+    "markdown-it-py==4.0.0",
+    "mdurl==0.1.2",
+    "Pygments==2.19.2",
+    "python-dotenv==1.2.2",
+    "readchar==4.2.1",
+    "rich==14.3.3",
+    "runs==1.3.0",
+    "wcwidth==0.6.0",
+    "xmod==1.9.0",
+]
+
+[project.scripts]
+dev-scaffolder = "scripts.scaffolder.scaffolder:main"
+
+[project.urls]
+Homepage = "https://github.com/Faisal-Sey/dev-scaffolder"
+Issues = "https://github.com/Faisal-Sey/dev-scaffolder/issues"
+
+[tool.setuptools.package-dir]
+"" = "src/dev-scaffolder"
+
+[tool.setuptools.packages.find]
+where = ["src/dev-scaffolder"]
+exclude = [
+    "venv*",
+    "temp*",
+    "*.egg-info",
+    ".env",
+    ".env*",
+    ".idea",
+    ".vscode",
+    ".git",
+    "*__pycache__*",
+    "*.pyc",
+    "dist",
+    "build"
+]
+
+[tool.setuptools.package-data]
+"*" = ["*.json"]

dev_scaffolder-0.0.1/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

dev_scaffolder-0.0.1/src/dev-scaffolder/constants/backend/python/base.py

@@ -0,0 +1,16 @@
+DJANGO_APP_URL_CONFIG = (
+    f"from django.urls import path\n"
+    f"from views import hello\n\n"
+    f"urlpatterns = [\n"
+    f"    path('', hello, name='hello'),\n"
+    f"]\n"
+)
+
+DJANGO_VIEW_FUNCTION_IMPORT_JSON_RESPONSE = "from django.http import JsonResponse\n\n"
+
+DJANGO_VIEW_FUNCTION_MESSAGE = '{"success": True, "message": "hello"}'
+
+DJANGO_VIEW_FUNCTION = (
+    f"def hello() -> JsonResponse:\n"
+    f"  return JsonResponse({DJANGO_VIEW_FUNCTION_MESSAGE})"
+)