fix: url containing dots were not correctly normalized with .html extension

[sumy7]

Summary

This PR fixes an issue where URLs containing dots were not correctly appended with the .html extension.

/guide/version-0.1
expect:
/guide/version-0.1.html
actual:
/guide/version-0.1

Related Issue

#933

Checklist

• Tests updated (or not required).
• Documentation updated (or not required).

[netlify]

✅ Deploy Preview for aquamarine-blini-95325f ready!

Name	Link
🔨 Latest commit	62e9a38
🔍 Latest deploy log	https://app.netlify.com/sites/aquamarine-blini-95325f/deploys/661735cec0689c0008b366da
😎 Deploy Preview	https://deploy-preview-934--aquamarine-blini-95325f.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 88 (🔴 down 4 from production) Accessibility: 97 (no change from production) Best Practices: 100 (no change from production) SEO: 92 (no change from production) PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[Timeless0911]

if there exists a url like /foo/bar.png, it will be added a .html in current logic? I'm not sure if there is such a scenario, may be we need to know what is the original extension judgment logic for?

@sanyuan0704 any context about this logic?

[sumy7]

if there exists a url like /foo/bar.png, it will be added a .html in current logic? I'm not sure if there is such a scenario, may be we need to know what is the original extension judgment logic for?

@sanyuan0704 any context about this logic?

you are right. We should check all the usages of this function. Or add a flag to control this action.

[sumy7]

I have reviewed all the places where the function normalizeHref is used. It appears to be used only for organizing href parameters or handling article links, and there is no case where it handles such as .png suffixes. I will reopen this PR for now, but further confirmation is needed from @sanyuan0704 .