Inconsistencies in the handling of `public_folder` in image paths: Discrepancies between expectations and results

[lorensansol]

• If I use public_folder: /foo
  • Expectation?: image: /foo/example.jpg
  • Reality: image: /foo/example.jpg ✅
• If I use public_folder: /foo/
  • Expectation?: image: /foo/example.jpg
  • Reality: image: /foo//example.jpg 🆗 It is ok because there is the previous option
• If I use public_folder: ''.
  • Expectation?: image: example.jpg ⬅️ I would especially like this
  • Reality: image: /example.jpg ❌
• If I use public_folder: /
  • Expectation?: image: /example.jpg
  • Reality: image: //example.jpg ❌

[lorensansol]

I also have problems with images in subdirectories

With media_folder: assets/media, I have this:

• If I use public_folder: '' and public_folder: /:
  • fondo.jpg ✅
  • /fondo.jpg ✅
  • base/logo.png ❌ 😱 No expected ⬅️ I would especially like this
  • /base/logo.png ❌ 😱 No expected
  • foo/fondo.jpg ❌ 🆗 Expected
  • /foo/fondo.jpg ❌ 🆗 Expected
  • foo/base/logo.png ❌ 🆗 Expected
  • /foo/base/logo.png ❌ 🆗 Expected

• If I use public_folder: /foo and public_folder: /foo/:
  • fondo.jpg ✅ 🤷
  • /fondo.jpg ✅ 🤷
  • base/logo.png ❌ 🤷
  • /base/logo.png ❌ 🤷
  • foo/fondo.jpg ✅
  • /foo/fondo.jpg ✅
  • foo/base/logo.png ✅
  • /foo/base/logo.png ✅

Working locally, when an image does not load, I get this error in the console:

error: Error handling {"branch":"main","action":"getMediaFile","params":{"branch":"main","path":"assets/mediabase/logo.png"}}: ENOENT: no such file or directory, open '/[PROJECT-PATH]/assets/mediabase/logo.png'