Files
browser-use/browser_use
reformedot c99e1bb41f refactor: improve type checking and linting script
- Updated `pyproject.toml` to enhance type checking configuration by refining the `exclude` list and adding an `include` section for better clarity.
- Modified `lint.sh` to run tools directly from the virtual environment, improving execution reliability and avoiding permission errors.
- Enhanced comments in `lint.sh` for better understanding of script functionality and usage.
2025-11-11 12:00:20 -08:00
..
2025-11-06 14:51:52 -08:00
2025-08-26 14:23:40 -07:00
2025-11-06 14:51:52 -08:00
2025-10-31 14:25:31 -07:00
2025-09-19 19:36:53 -07:00
2025-10-31 21:02:38 -07:00
2025-11-03 14:49:12 -08:00
2025-10-31 14:25:31 -07:00
2025-09-16 22:27:45 -07:00
2025-03-28 18:11:36 -07:00
2025-10-30 20:05:32 -07:00
2025-09-23 20:03:26 -07:00
2025-07-21 12:59:11 +02:00
2024-11-06 18:18:00 +01:00

Codebase Structure

The code structure inspired by https://github.com/Netflix/dispatch.

Very good structure on how to make a scalable codebase is also in this repo.

Just a brief document about how we should structure our backend codebase.

Code Structure

src/
/<service name>/
models.py
services.py
prompts.py
views.py
utils.py
routers.py

    	/_<subservice name>/

Service.py

Always a single file, except if it becomes too long - more than ~500 lines, split it into _subservices

Views.py

Always split the views into two parts

# All
...

# Requests
...

# Responses
...

If too long → split into multiple files

Prompts.py

Single file; if too long → split into multiple files (one prompt per file or so)

Routers.py

Never split into more than one file