Shawn Erquhart

Context: > But I guess you can avoid them by setting the config path. Which you _should_ be able to do via config (manual init) For example: ```yaml config_path: "config.toml"...

True, guess we could just toss in the logic.

@tech4him1 that PR opened the door for custom naming of the config file, and provided a means for specifying a non-yaml format, but didn't include support for actually handling non-yaml...

I'll be going through PR's soon, but I think the best way to handle this is probably by some cooperation between the media library and the image widget preview component....

Widget preview components provide a default preview for an individual field. We would make the image widget provide the image as expected by default. If someone _wants_ the actual field...

Yep, those are `img` elements, if you check their `src` you'll see what they're looking for and can determine why it's not there. Either the image wasn't deployed, your CMS...

I've long thought we needed to split the UI components out so they could be replaced with custom ones, but I bet what people really want is just to change...

The only complicated part is doing this in a way that works for extensions, namely widgets. Sent with GitHawk

They're internal, no outside access at the moment.

We've made determinations in the past not to use test coverage as a metric. cc/ @marccampbell