[Feature Request] defaultScope... types add undefined keyword

[Mister-Hope]

✅ Checklist

• I am using the latest version
• I have searched FAQ

📄 System Info

not needed

🔎 Description

The code is similar to the ones in docs: https://cz-git.qbb.sh/zh/recipes/default-scope#defaultscope

In another word, users can not guarantee a default scope could be inferred from the commit, and some thing like the following is too ugly, as the tool support undefined, it shall add it to types.

Note: You should also check other options as well as I believe similar issues might exist

🔗 Reproduction link / repo:

No response

[Zhengqbbb]

But I defined already includes undefined

[Mister-Hope]

I have a stricter tsconfig.json, where a?:type differs from a?:type|undefined, the former only allow to be absent, or with a exact type.

BTW, I suggest you opt-in this behavior in your project, as a: undefined might break the following:

const my plugin = ({ a = 1 }) => {
  // expect a to be number here
}

[Zhengqbbb]

😅 PR welcome

[Mister-Hope]

Ref: https://www.typescriptlang.org/tsconfig/#exactOptionalPropertyTypes This is recommended by typescript team so I would suggest you add this to your tsconfig.json and perform a full refactor.

The problem is that I am not sure if all options can be passed with undefined without causing issues, like I said before, declaring it may cause issues:

I suggest you opt-in this behavior in your project, as a: undefined might break the following:

const my plugin = ({ a = 1 }) => {
  // expect a to be number here
}

It's fine for me to send a PR fixing defaultScope ONLY, but I think a full check and fix should be better. :)