René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Mention why we don't use pydantic in FAQ","articleBody":"\u003e \u003e I guess I misinterpreted the ticket. I thought it was creating an issue on a downstream project.\r\n\u003e \u003e My point is that a ticket is a burden on (volunteer) maintainers. Because we pin dependencies, if users add commitizen as a dev-dependency, we limit what they can install. pydantic is a widely used dependency, we would have to rush into supporting v3 (depending on how we pin it). This PR doesn't make use of much iterfaces from pydantic, but by having it available, we are telling other contributors: yes, you can use the full pydantic featureset. It's a long term issue FMPOV\r\n\u003e \u003e This would be a clearer issue: #1249\r\n\u003e \r\n\u003e You're right. I intention of this PR was that I just wanted a more strict type for `Questions`. The runtime check is not needed.\r\n\u003e \r\n\u003e Let me close this PR and use `TypedDIct` to address the issue.\r\n\r\nMaybe we could mention this in our FAQ as well 🤔\r\n\r\n_Originally posted by @Lee-W in https://github.com/commitizen-tools/commitizen/issues/1467#issuecomment-2926398577_\r\n            ","author":{"url":"https://github.com/bearomorphism","@type":"Person","name":"bearomorphism"},"datePublished":"2025-06-01T07:58:29.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/1488/commitizen/issues/1488"}