Match error: Unknown key in field

[EdoElgx]

I'm having an issue:

• Give an expressive description of what is went wrong When uploading a file with a custom schema, it fails with this error:

  {
  "message": "Match error: Unknown key in field abstract",
  "path": "abstract",
  "sanitizedError": {
      "isClientSafe": true,
      "error": 400,
      "reason": "Match failed",
      "message": "Match failed [400]",
      "errorType": "Meteor.Error"
  },
  "errorType": "Match.Error"
  }

• Version of Meteor-Files you're experiencing this issue

  ostrio:files              2.3.3
  aldeed:collection2        3.5.0
  aldeed:simple-schema      1.13.1

• Version of Meteor you're experiencing this issue 2.15

• Where this issue appears? OS (Mac/Win/Linux)? Browser name and its version?

  Intel macOS 14.3.1 Sonoma.
  Brave 1.63.169 Chromium 122.0.6261.111 (Official Build)

• Is it Client or Server issue? Client. It seems the schema is validated at the client.

Client Code:

      const file = event.target.files[0]
      if (!file) {
        console.log('No file')
        return
      }
      const uploadInstance = AttachmentsCollection.insert({
        file,
        chunkSize: 'dynamic',
        abstract: 'I am just testing'
      }, false) // <== IT FAILS HERE
      console.log('Setting upload instance', uploadInstance) // <== IT'S NEVER SHOWN
      uploadInstance.on('start', () => {
        setUploadStatus(t('institutions.agreements.upload.started'))
      })
      // ...

Server Code:

import { Meteor } from 'meteor/meteor'
import { FilesCollection } from 'meteor/ostrio:files'

const attachmentSchema = {
  ...FilesCollection.schema,
  abstract: { type: String, optional: true }
}

const AttachmentsCollection = new FilesCollection({
  collectionName: 'attachments',
  allowClientCode: false,
  schema: attachmentSchema,
  storagePath: function () {
    if (process.env.NODE_ENV === 'development') {
      return '../attachments'
    } else {
      return process.env.ATTACHMENT_LOCATION
    }
  },
  debug: process.env.NODE_ENV === 'development'
})

AttachmentsCollection.collection.attachSchema(AttachmentsCollection.schema)

• Post Client and/or Server logs with enabled debug option

  core.js:108 [FilesCollection] [insert()]
  match.js:42 Uncaught errorClass {message: 'Match error: Unknown key in field abstract', path: 'abstract', sanitizedError: errorClass, errorType: 'Match.Error', stack: 'Error: Match error: Unknown key in field abstract\n…s/ui/components/InstitutionAgreements.jsx:581:69)'}

[dr-dimitru]

Hello @EdoElgx ,

Remove abstract: 'I am just testing' line from:

const uploadInstance = AttachmentsCollection.insert({
  file,
  chunkSize: 'dynamic',
}, false);

If you need to pass additional data along with a file use meta object, like:

const uploadInstance = AttachmentsCollection.insert({
  file,
  chunkSize: 'dynamic',
  meta: {
    abstract: 'I am just testing'
  }
}, false);

Hope that helps, let me know

[EdoElgx]

Thank you, @dr-dimitru. I'll try that.

Is there any way to validate what I pass in the meta property?

[dr-dimitru]

@EdoElgx yes you can define schema for meta object

[EdoElgx]

Thanks @dr-dimitru I'll try that.

Inserting without schema worked perfectly.

[dr-dimitru]

@EdoElgx I'm glad it was solved quickly