Indexes do not work in objects named "properties"

[grantcodes]

Case

Bug

Issue

Indexes do not work in objects named "properties"

Info

• Environment: Node.js
• Adapter: IndexedDB

Code

  const collection = await myDatabase.collection(
    name: "posts",
   schema: {
      version: 0,
      id: 'post',
      type: 'object',
        properties: {
          type: 'object',
          properties: {
            name: {
              type: 'string',
              index: true,
            },
          },
        },
      },
  );

I am storing microformats2 json which defines a property named "properties", if you set an index inside that property RxDB will throw an error with the schema, even though it is totally valid

"SchemaCheck: given index is not defined in schema" is the thrown error.

It definitely is caused by replacements going on here:

rxdb/src/plugins/schema-check.js

Line 241 in 1b44b63

const schemaObj = objectPath.get(jsonID, 'properties.' + key.replace(/\./g, '.properties.'));

I am not sure what would be required to fix it, you would likely need to check for the nesting of properties.properties somehow.

[pubkey]

You have nested properties directly into properties. I do not think this is valid json-schema. How would an object look that matches your schema?

EDIT: aah, now I know what you meant to do. But what does the second type do?

[grantcodes]

I'm not sure what you mean by "the second type"

But the data would look something like this:

{
  type: ['h-entry'],
  properties: {
    name: ['Title']
    content: ['Post content']
  }
}

I simplified the schema to try and just show the part relevant to the bug. But in reality it is much more complex

[pubkey]

Ok this is definitely a bug. A PR would be welcomed.

[pubkey]

@grantcodes thx for pointing this out. I fixed it in the referenced commit.

[grantcodes]

Awesome! Thanks for the quick fix @pubkey