Skip to content

Commit f4b7d4e

Browse files
committed
docs(faq): fix markdown in Pydantic FAQ
Closes #1488
1 parent a5073f2 commit f4b7d4e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/faq.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -90,13 +90,13 @@ More discussion can be found in issue [#318](https://github.com/commitizen-tools
9090

9191
## Why don't we use Pydantic?
9292

93-
While **Pydantic** is a powerful and popular library for data validation, we intentionally avoid using it in this project to keep our dependency tree minimal and maintainable.
93+
While Pydantic is a powerful and popular library for data validation, we intentionally avoid using it in this project to keep our dependency tree minimal and maintainable.
9494

9595
Including Pydantic would increase the chances of version conflicts for users - especially with major changes introduced in Pydantic v3. Because we pin dependencies tightly, adding Pydantic could unintentionally restrict what other tools or libraries users can install alongside `commitizen`.
9696

9797
Moreover we don't rely on the full feature set of Pydantic. Simpler alternatives like Python's built-in `TypedDict` offer sufficient type safety for our use cases, without the runtime overhead or dependency burden.
9898

99-
In short, avoiding **Pydantic** helps us:
99+
In short, avoiding Pydantic helps us:
100100

101101
- Keep dependencies lightweight
102102
- Reduce compatibility issues for users

0 commit comments

Comments
 (0)