Emoji (character or code) in heading causes broken TOC link

[benji-bou]

When adding emoji in a Header the generated link in TOC is broken.
It seems that (in the case of the warning emoji) there is extra code %E2%9A%A0 and if the "shortcode" is used it add an extra "warning" at the end of link

The link is correct inside Visual Studio itself, but the visual studio preview and on gitlab the link is broken

To fix the link (in this particular case (with warning emoji)) we need to manually disable the "markdown.extension.toc.updateOnSave"
and remove the extra code %E2%9A%A0 or remove the warning (in case of "shortcode") in the generated toc link

Add a Header with the Warning Emoji and generate TOC
--> It doesn't work when generated

- [Test ⚠️](#test-%E2%9A%A0%EF%B8%8F)
- [Test \:warning\:](#test-warning)

## Test ⚠️
## Test 2 :warning:

--> It works when

- [Test ⚠️](#test-EF%B8%8F)
- [Test \:warning\:](#test-)

## Test ⚠️
## Test 2 :warning:

Best

[yzhang-gh]

I see. That is because the anchor/link will be encoded (just like space will be encoded to %20).
related #90.

[benji-bou]

Hi,

Ok, you think the encodeUrl you want to implement will fix this problem as well? Do you have a due date for this fix?

Good extension By the way 👍
Best

[yzhang-gh]

I will get back to you on Feb 25 😉

[yzhang-gh]

If you set encodeUri to false, it will be

# Test ⚠️
# Test 2 :warning:

- [Test ⚠️](#test-⚠️)
- [Test 2 :warning:](#test-2-warning)

That means ⚠️ will remain the same rather than being encoded into %%E2%9A%A0...

---

The upcoming vscode monthly build has some breaking changes so I would like to update this extension later. But if you need, I can also package a beta version in advance.

[yzhang-gh]

v1.1.0 released