[Content] Throw on relative image usage

[bholmesdev]

Changes

We decided relative image resolution was out-of-scope for the Content Collections RFC. Throw on relative image paths in src/content/ for Markdown and MDX.

Testing

Manual testing

Docs

N/A - Already documented that Markdown and MDX are the only allowable files.

[changeset-bot]

🦋 Changeset detected

Latest commit: c2f2435

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[andersk]

Can this check be optional? Right now relative paths are the only way to reference images from *.md that works with arbitrary values of BASE_URL. It’s not ideal that they’re relative to the output URL rather than the input file, but better than impossible.

[natemoo-re]

LGTM!

[natemoo-re]

Can this check be optional? Right now relative paths are the only way to reference images from *.md that works with arbitrary values of BASE_URL. It’s not ideal that they’re relative to the output URL rather than the input file, but better than impossible.

I think unfortunately, this is why this setting can't be optional. We're trying to protect against anyone from relying on the current unspecified behavior. The eventual plan is to specify the correct behavior for relative paths, which likely means that they'll be resolved and treated as actual assets. That would also solve the BASE_URL issue, but have lots of other benefits as well.