Any filter condition including a dot (.) in the property name is stripped

[fra967]

Expected behavior

Any query targeting a Mixed field to be passed to the database

Actual behavior

Queries including a valid path are stripped

For example

localhost:3000/1.0/articles/celebrity?page=1&count=1&filter={"subtitle":"test","editor.editor_name":"test"}

is passed to Mongo as

        "query" : {
                "subtitle" : /^test$/i,
                "apiVersion" : "1.0"
        },

Note that editor.editor_name is not present

Steps to reproduce the problem

It seems that API queries are validated against the schema, and if they include an invalid reference they are stripped. However editor in this case is Mixed, and contains other subdocuments, which are individually validated in the schema
https://github.com/dadiplus/bauer-lifestyle-serama/blob/dev/workspace/collections/1.0/articles/collection.celebrity.json

It didn't seem possible to enforce validation on a subelement in the previous API version, but it had to be written at root level. The document in the sample request above includes this field

        "editor" : {
                "editor_id" : "566f8a14975babee0989528c",
                "editor_name" : "Francesco Iannuzzelli"
        },

In any case, validation shouldn't be enforced on queries targeting a Mixed field, as that could contain anything. This is particularly applicable to dates that are stored as Mongo dates, for example

        "publicationDate" : {
                "sec" : 1462119300,
                "usec" : 0
        },

(this is actually the origin of this issue, as queries targeting the publicationDate.sec timestamp fail in Bauer Lifestyle)

Package details

1.3.0

[fra967]

I would expect the same to happen in an Object field (that is, being able to query a sub-element)

[eduardoboucas]

I believe this fixes it. Can you have a look @jimlambie?

Thanks!

[jimlambie]

Closed by commit 7270f94