Using field Image results in unnecessary repeating of the slug in the (collection) entry

[jackverstappen]

I'm using keystatic in an Astro project, and the usage of the field Image is causing me some challenges, which can be overcome, but I see it as a missed opportunity to make things smoother.

When using field Image, a selected image file gets stored with the schema name and (in case of collection) also preceded with the slug.

For example, with something like

collections: {
    archive: collection({
      label: 'Archive',
      slugField: 'title',
      path: 'src/content/archive/*/',
      entryLayout: 'content',
      format: { contentField: 'description' },
      schema: {
        title: fields.slug({ name: { label: 'Title' } }),
        cover: fields.image({
          label: 'Cover Image',
          directory: 'src/content/archive',
          publicPath: './',
        }),
        media: fields.array(
          fields.image({
            label: 'Image',
            directory: 'src/content/archive',
            publicPath: './',
          }),
          {
            label: 'Media',
            itemLabel: props => props.value?.filename ?? 'Image',
          }
        ),
      },
    }),

would end up (as an example) as:

---
title: project X
cover: ./project-x/cover.png
media:
  - ./project-x/media/0.png
  - ./project-x/media/1.png
  - ./project-x/media/2.png
  - ./project-x/media/3.png
  - ./project-x/media/4.png
tags:
  - works
---

In other words, the ```slug`` of the collection entry is unnecessary mentioned throughout the frontmatter. Any idea on how to overcome this?