fix: create post with a path composed of numbers throw an error

[D-Sketon]

What does it do?

fix #4334

Screenshots

Pull request tasks

• Add test cases for the changes.
• Passed the CI test.

[github-actions]

How to test

git clone -b fix_4334 https://github.com/D-Sketon/hexo.git
cd hexo
npm install
npm test

[coveralls]

Coverage increased (+0.04%) to 98.778% when pulling 2ec8682 on D-Sketon:fix_4334 into 58a8f8c on hexojs:master.

[stevenjoezhang]

There will be an edge case: --path 0x100 will become string '256', not '0x100'.

You can try to change the code here: https://github.com/hexojs/hexo-cli/blob/5c5fc8fe2fc781a557a30f1bf2043502825f173c/lib/hexo.ts#L18

minimist(process.argv.slice(2), { string: ['_', 'p', 'path'] })

should work

[stevenjoezhang]

See also hexojs/hexo-cli#200

[D-Sketon]

@stevenjoezhang should slug also be added to this code?
For example: hexo new page --slug 0x404 will generate 1028.md

[stevenjoezhang]

@D-Sketon Yes, the slug should also have a string type

You can add other test cases like #4363

[D-Sketon]

@stevenjoezhang I'm a bit confused, do I just need to add extra test cases in this PR?
I have tried to add test cases like #4363, but they all fail. It seems that the tests all skip hexo-cli by using lib\plugins\console\new.js directly

[stevenjoezhang]

It's tricky to cover this situation with unit tests, need to hook process.argv somehow

[D-Sketon]

Superseded by #5465