This is the beginning of the foundational implementation of Air, which follows practices we've explored in Air and on other frameworks. It allows Air developers to more easily take on more significant projects.

For database setup, in the name of simplicity this version will use plain asyncpg+dbmate. However, I'll write it in such a way that we can add support for other async-friendly options like SQLModel and TortoiseORM.

Command: air init

Creates a new Air project

Usage: air init mysite

While other templates can be provided, the default project design is:

├── .github  # Includes basic QA for GitHub 
├── .gitignore
├── app  # Various application logic components
│   └── routes/
├── config.py  # Configuration at the project level
├── db/  # Database schema and migrations
│   └── schema/
│   └── migrations/
├── main.py  # Main entry point for the project
├── public  # CSS, JS, HTML files that are forward facing
├── scripts  # Where to put command-line actions
└── tests  # Source for all tests, should mirror the file design

Pull request type

Please check the type of change your PR introduces:

• Bugfix
• New feature
  • Core Air (Air Tags, Request/Response cycle, etc)
  • Optional (Authentication, CSRF, etc)
  • Third-Party Integrated (Cookbook documentation on using Air databases or a task manager, etc)
  • Out-of-Scope (Formal integration with databases, external task managers, or commercial services etc - won't be accepted, please create a separate project)
• Refactoring (no functional changes, no api changes)
• Chore: Dependency updates, Python version changes, etc.
• Build related changes
• Documentation content changes
• Other (please describe): Architecture change

Pull request tasks

The following have been completed for this task:

• Code changes
• Documentation changes for new or changed features
• Alterations of behavior come with a working implementation in the examples folder
• Tests on new or altered behaviors

Checklist

• I have run just test and just qa, ensuring my code changes passes all existing tests
• I have performed a self-review of my own code
• I have ensured that there are tests to cover my changes