I've had (I think) a similar issue. In particular, if my pseudo-pattern is modifying a value that is multiple levels deep in _data.json, the entire parent object is replaced instead of just the chosen attribute.

For example, if this is the code in _data.json…

{
    "callout" : {
            "headline" :  "Sample headline",
            "content" : "Sample content."
    }
}

…and I have a partial called callout-block.mustache, I can put this code into callout-block.json and it will work fine:

{
    "callout" : {
            "content" : "New content."
    }
}

However, if I try to create a pseudo-pattern using a file called callout-block~new-content.json, the same code will give me a blank pattern. Adding the "headline" attribute back into the file will cause it to work again, but it requires specifying text for this particular pseudo-pattern.

It seems that in pseudo-patterns with multiple levels of depth, the entire object (in this case "callout") is replaced instead of just the listed attributes.

Pseudo patterns don't work in view all #272

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions