How to insert data into JSON fields using the Local API with PostgreSQL backend?

[torse]

Can somebody help and describe how to add JSON to a collection with the Local API using the PostgreSQL backend?

I've set up a field in a collection using type:json and it is correctly created as jsonb in the Postgres table. However when I try to add JSON with the Local API it is simple not stored in the DB. There is no error during the insert but the field is empty in the DB, Admin UI and hence not retrievable with the REST API. Is this not yet supported (in latest v3beta) or am I doing something wrong?

Collection "Maps":

export const Maps: CollectionConfig = {
  fields: [
    {
      name: 'map',
      type: 'json',
      required: false,
    },
    ...

seed.ts:

const map: Map = {
    id: 0,
    createdAt: new Date().toISOString(),
    updatedAt: new Date().toISOString(),
    slug: "some_slug",
    title: "Some Title",
    description: "Some Description",
    map: JSON.parse(fs.readFileSync(dir + '/' + data.mapFile, 'utf-8')),
  }
...
await payload.create({
    collection: collection,
    data: map,
})

Console log just before payload.create:

console.log("Map:", map) 
->
Map: {
  id: 0,
  createdAt: '2024-10-08T17:53:03.914Z',
  updatedAt: '2024-10-08T17:53:03.914Z',
  slug: '...',
  title: '...',
  description: '...',
  map: {
    view: {
      type: 'map',
      datasets: [Array],
      activeDatasets: [Array],
      extent: [Object],
      aois: [Array]
    }
  },

DB (via psql):

db # \d maps
                                         Table "public.maps"
   Column    |            Type             | Collation | Nullable |             Default              
-------------+-----------------------------+-----------+----------+----------------------------------
 id          | integer                     |           | not null | nextval('maps_id_seq'::regclass)
 slug        | character varying           |           |          | 
 title       | character varying           |           | not null | 
 preview_id  | integer                     |           |          | 
 description | character varying           |           |          | 
 updated_at  | timestamp(3) with time zone |           | not null | now()
 created_at  | timestamp(3) with time zone |           | not null | now()
 map         | jsonb                       |           |          | 
Indexes:
    "maps_pkey" PRIMARY KEY, btree (id)
    "maps_created_at_idx" btree (created_at)
    "maps_slug_idx" btree (slug)
Foreign-key constraints:
    "maps_preview_id_images_id_fk" FOREIGN KEY (preview_id) REFERENCES images(id) ON DELETE SET NULL
Referenced by:
    TABLE "maps_maps" CONSTRAINT "maps_maps_parent_id_fk" FOREIGN KEY (_parent_id) REFERENCES maps(id) ON DELETE CASCADE
    TABLE "payload_locked_documents_rels" CONSTRAINT "payload_locked_documents_rels_maps_fk" FOREIGN KEY (maps_id) REFERENCES maps(id) ON DELETE CASCADE
    
# select id,map from maps;
 id | map 
----+-----
  1 | 
(1 row)

edit: typo and added console.log on map object

[torse]

Well, my mistake. The above actually works.

The problem in my case was a typo in another select field of the collection that had a wrong/not supported option. After fixing the typo, the JSON is correctly stored in the DB. It would be helpful though, if the local api would thrown an error instead of silently ignoring this.

Here is the more complex example using a json and the select field within an array:
Collection maps:

export const Maps: CollectionConfig = {
    ...
    {
      name: 'maps', // required
      type: 'array', // required
      fields: [
        {
          name: 'format',
          type: 'select',
          options: ['format1', 'format2'],
          required: true,
        },
        {
          name: 'map',
          type: 'json',
          required: true,
        },
      ],
    },

seed.ts:

  const map: Map = {
    ...
    maps: [
      {
        format: "format1",
        map: JSON.parse(fs.readFileSync(dir + '/' + data.mapFile1, 'utf-8')),
      },
      {
        format: "format2", // <- using a wrong option like 'format3' silently ignoring the insert and results in an empty DB column
        map: JSON.parse(fs.readFileSync(dir + '/' + data.mapFile2, 'utf-8')),
      },
    ],
  }