Skip to content

nested optional resolving issues #49

@niallroche

Description

@niallroche

when attempting to use an {{#optional }} element inside of a concept that is part of a clause it appears there is a resolution issue for a property of that object. See attached files ready to paste into template playground that illustrate multiple attempts to get the uri property to resolve correctly with various combinations of clause/with/optional it will resolve with inline typescript, however a way of resolving via optional would be cleaner.

data.json
grammar.tem.md
model.cto.txt

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions