Flask patterns -- application factory, blueprints, error handlers, extensions, request lifecycle, configuration, logging, CLI commands
98
98%
Does it follow best practices?
Impact
98%
1.28xAverage score across 5 eval scenarios
Passed
No known issues
A small team wants a task management backend built with Flask. They need a REST API where users can create projects and add tasks to them. Each task has a title, description, status (todo/in_progress/done), and priority (low/medium/high). Each project has a name and description.
The team specifically wants:
Build the complete Flask application with endpoints for:
POST /api/projects -- create a projectGET /api/projects -- list all projectsGET /api/projects/<id> -- get a single projectPOST /api/projects/<id>/tasks -- create a task in a projectGET /api/projects/<id>/tasks -- list tasks in a projectPATCH /api/tasks/<id> -- update a task's status or priorityProduce Python source files in a task-manager/ directory:
app/__init__.py -- application factoryapp/extensions.py -- extension instancesapp/errors.py -- custom exceptions and error handler registrationapp/routes/projects.py -- project blueprintapp/routes/tasks.py -- task blueprintapp/db.py -- in-memory data storetests/conftest.py -- test fixturesrun.py -- entry pointrequirements.txtDo not run pip install or start the server.