Closed trinhpham closed 11 months ago
I think it's because #1103 . Hm... took me one day to figure it out.
Please consider to revert it so people can migrate from v1 to this version.
The v1 behavior is actually breaking markdown. An <img src="a/b.png" />
should be a relative link that points to b.png under current folder's "a" sub dir.
We done the fix so that existing markdown contents like wiki and blogs could be served by VuePress out of box without adding ./
in every links. That's stopping more people to start using VuePress than people who migrates from V1.
Please consider to revert it so people can migrate from v1 to this version.
The usage of alias should be actually considered abnormal, so should requires extra handling. We still allows you to use alias in img tag, so you should consider migrating all markdown format to html tags.
This is a disappointing breaking change. Having to migrate the hundreds of markdown docs to a new image format will be incredibly time consuming. Some sort of migration path option from V1 would be nice for your existing users.
When it's this much work it creates a situation where, along with measuring the effort of migrating we should look at other options.
At a minimum put this breaking change in the migration docs. It took me multiple days to find this and the existing docs are misleading that it could be made to work.
I understand your disappointment, but I think that v1 support for this is unreasonable because far more people are complaining why should every relative markdown image link should be enforced starting with ./
We will mention this in migration docs, besides, you may try to use regexp to help you check and convert existing ones to new syntax, that should not be a hard work.
Description
Upgrade to latest version broken sites that use image alias.
Reproduction
Use image alias in markdown
Used Package Manager
yarn
System Info