[3.0] Properly support file UUIDs [Clicking on a file/image link does not work]

[tobimori]

[fabianmichael]

I am aware of this … I tried to get real previews, but it seems to be next to impossible by now, since this would mean using widgets inside of CodeMirror and those seemingly cannot be loaded async and I would also need another endpoint to fetch page titles, panel links etc.

What do you think? Should we use filenames/page names instead? Would at least make things way more readable, but we would loose UUID support within the editor. I’m pretty unsure that would be the right thing to do here.

[tobimori]

This is my first time using the Markdown field, or rather KirbyText at all since Writer/Blocks came out, as this project has a large library of "legacy" blog articles in markdown format - so maybe I'm not the most active user here.

Usually, I have a centralized asset directory and allow slug editing even for singleton pages, by relying on UUIDs. So I'd heavily prefer having proper UUID support, even if this requires some extra work.

I also assume "the way forward" with Kirby will be UUIDs everywhere.

[tobimori]

i'd also would want to use the markdown syntax over the kirbytag, but that's a different issue...

[fabianmichael]

@tobimori Is there something like panel Links with UUIDs? Otherwise we would have to implement an API endpoint or use fetch to resolve UUIDs first, which would also include funny stuff like permission management … I am not willing to go into that. BTW, you can enable Markdown syntax for links. If you feel like any of these features is important for you, feel free to make a contribution. I am happy to help you getting more familiar with the code.