remove the searchParams when writing comments into issue

[Mr-Sheep]

When utterances creates comments inside a issue, it will automatically include the searchParams within the link like this: https://example.com?fname=Nicky&lname=Parsons I was wondering if utterances can add the option to remove the searchParams from the link?

[hifocus]

Further from this, I am not sure (now it looks like it doesn't) whether utterances treat example.com/something/else.html and example.com/something/else and example.com/something/else/ the same.

For a use case, some JAMstack hosting services respect the .html file generated, and present the page in address bar exactly as its extension, however, some others, which are minorities, treat /something.html the same as /something, and will redirect users from the .html page to the /something page.

Also, some Wordpress users may find their url structure is example.com/something/else/' upon migration, such as from a blog framework to another, or indeed between hosting services, url structure may vary slightly however the content of the page is exactly the same.

I worry that once such structural change occurs, after the change utterances will not recognise the pathname. In this case, a minor change to the code will be appreciated.

I will try at another time to try to implement this minor feature.