Skip to content

Define Origin as a list #98

@swhume

Description

@swhume

The define.json has origin as a dictionary, not a list. So there's just 1 per Item. Typically, multiple origins are addressed in VLM, but the spec does allow for multiple def:Origins on a single variable. I assume we'll want to allow for multiple origins (make it a list), but we can discuss whether or not it's really needed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestteam-DefineGenDefine Generation feature team
    No fields configured for Feature.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions