Backend
Initialize the Project
python -m venv ~/.virtualenvs/myproject
source ~/.virtualenvs/myproject/bin/activate
pip install freenit[dev]
freenit.sh myproject
cd myproject
bin/devel.sh
You will get just a few basic tests on initialization. You can run them with:
bin/test.sh
To write more tests, add test_<name>.py
to tests
directory.
Model
Let's say you want to add the simplest model for blog post with only title and
contents. In your project's models
directory you need to create blog.py
:
import ormar
from freenit.config import getConfig
from freenit.models.base import BaseModel
from freenit.models.metaclass import AllOptional
config = getConfig()
auth = config.getUser()
class Blog(BaseModel):
class Meta(config.meta):
pass
id: int = ormar.Integer(primary_key=True)
title: str = ormar.String(max_length=1024)
content: str = ormar.Text()
user: auth.UserModel = ormar.ForeignKey(auth.UserModel)
class BlogOptional(Blog, metaclass=AllOptional):
pass
Please note two things: BaseModel
is Freenit class not Ormar and
BlogOptional
is for PATCH method so all it's fields are the same as Blog
except they are optional. The reason for this is that Ormar models are not just
for DB operations, but for validating JSON input and parsing objects into JSON.
Endpoint
In api
directory of your project add blog.py
with the following content:
from typing import List
import ormar
from fastapi import HTTPException
from freenit.config import getConfig
from freenit.router import route
from ..models.blog import Blog, BlogOptional
config = getConfig()
auth = config.getUser()
@route('/blogs', tags=['blog'])
class BlogListAPI():
@staticmethod
async def get() -> List[Blog]:
return await Blog.objects.all()
@staticmethod
async def post(
blog: Blog,
user_data: auth.UserDB = Depends(current_user.active),
) -> Blog:
user = await auth.UserModel.objects.get(id=user_data.id)
blog.user = user
await blog.save()
return blog
@route('/blogs/{id}', tags=['blog'])
class BlogDetailAPI():
@staticmethod
async def get(id: int) -> Blog:
try:
blog = await Blog.objects.get(pk=id)
except ormar.exceptions.NoMatch:
raise HTTPException(status_code=404, detail="No such blog")
return blog
@staticmethod
async def patch(id: int, blog_data: BlogOptional) -> Blog:
try:
blog = await Blog.objects.get(pk=id)
await blog.patch(blog_data)
except ormar.exceptions.NoMatch:
raise HTTPException(status_code=404, detail="No such blog")
return blog
@staticmethod
async def delete(id: str) -> Blog:
try:
blog = await Blog.objects.get(pk=id)
except ormar.exceptions.NoMatch:
raise HTTPException(status_code=404, detail="No such blog")
await blog.delete()
return blog
@route
is
Freenit's decorator to make it easy to write class based endpoints. As FastAPI
itself has great support for function based endpoints, the idea was to make
it possible for developer to choose between functions and classes. With Freenit
you can write any style you want. Also note that class methods are static
(decorated with @staticmethod
) because API classes will never create an object.
Or in other words, methods are going to be called on class, not object. Return
value type hinting is important. It will tell Freenit what object is returned
from the method and how to convert it to JSON. Alternatively, you can use
responses
attribute in @route
like the following:
@route('/blogs', tags=['blog'], responses={'post': Blog})
class BlogListAPI():
@staticmethod
async def post(
blog: Blog,
user_data: auth.UserDB = Depends(current_user.active),
) -> Blog:
user = await auth.UserModel.objects.get(id=user_data.id)
blog.user = user
await blog.save()
return blog
@route
. Although
method also has return type hinting, if given, responses object has priority in
denoting how to serialize object to JSON. It is the same as FastAPI's
response_model
argument and it exists for situations when type hinting is not
expressive enough.
If you need to include and/or exclude fields, you can use get_pydantic()
and
exclude/include
to get what you want. For example:
@route('/blogs', tags=['blog'])
class BlogListAPI():
@staticmethod
async def post(
blog: Blog,
user_data: auth.UserDB = Depends(current_user.active),
) -> Blog.get_pydantic(exclude={'id'}):
user = await auth.UserModel.objects.get(id=user_data.id)
blog.user = user
await blog.save()
return blog
Blog.get_pydantic()
can be used in type hinting as well as argument
to responses
object in @route
.
DB Migration
To connect it all, you need to add the following to api/__init__.py
:
import myproject.api.blog
After that you need to create migration. To do that run the following command
from myproject
directory:
alembic revision --autogenerate -m blog
alembic/versions
and format it with
black. Next time you run bin/devel.sh
that migration will be applied.
Now you should see Blog endpoint in Swagger