From 662bd641b821b6724763f8503b03481459b6e1cf Mon Sep 17 00:00:00 2001 From: Soof Golan <83900570+soof-golan@users.noreply.github.com> Date: Tue, 4 Jun 2024 02:56:30 +0300 Subject: [PATCH] =?UTF-8?q?=E2=9C=8F=EF=B8=8F=20Fix=20broken=20link=20to?= =?UTF-8?q?=20`@dataclass=5Ftransform`=20(now=20PEP=20681)=20in=20`docs/fe?= =?UTF-8?q?atures.md`=20(#753)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Sebastián Ramírez Co-authored-by: Patrick Arminio --- docs/features.md | 12 +----------- 1 file changed, 1 insertion(+), 11 deletions(-) diff --git a/docs/features.md b/docs/features.md index f84606b..f0d5692 100644 --- a/docs/features.md +++ b/docs/features.md @@ -36,20 +36,10 @@ You will get completion for everything while writing the **minimum** amount of c You won't need to keep guessing the types of different attributes in your models, if they could be `None`, etc. Your editor will be able to help you with everything because **SQLModel** is based on **standard Python type annotations**. -**SQLModel** even adopts currently in development standards for Python type annotations to ensure the **best developer experience**, so you will get inline errors and autocompletion even while creating new model instances. +**SQLModel** adopts PEP 681 for Python type annotations to ensure the **best developer experience**, so you will get inline errors and autocompletion even while creating new model instances. -/// info - -Don't worry, adopting this in-development standard only affects/improves editor support. - -It doesn't affect performance or correctness. And if the in-progress standard was deprecated your code won't be affected. - -Meanwhile, you will get inline errors (like type checks) and autocompletion on places you wouldn't get with any other library. 🎉 - -/// - ## Short **SQLModel** has **sensible defaults** for everything, with **optional configurations** everywhere.