How to avoid having resources nested under Prisma in navigation?

[whatuserever]

I'm just getting started with AdminJS using Express and Prisma. Following the docs for adding Prisma resources, my AdminJSOptions looks as follows:

const options: AdminJSOptions = {
  componentLoader,
  rootPath: '/admin',
  resources: [
    {
      resource: { model: getModelByName('User'), client: prisma },
    },
  ],
};

However, this results in the resource being nested under Prisma:

I can't figure out how to avoid this. I tried the instructions here, but this simply renames Prisma to something else.

[dziraf]

1. Nesting under some name:

navigation: { name: 'xxx' }

2. Nesting under some name with icon (this is the default conifguration where name is usually your ORM):

navigation: { name: 'xxx', icon: 'Activity' }

3. Not nesting under anything:

navigation: null

4. Not nesting but having an icon:

navigation: { icon: 'Activity' }

You can use PascalCase names of icons from: https://feathericons.com/

[whatuserever]

Thanks! Appreciate the quick the response :)

Though, I'm curious why the default behavior (aka without explicitly defining options or navigation) is equivalent to

navigation: {
  name: 'Prisma', // Adapter?
  icon: 'Archive',
},

instead of defaulting to

navigation: null