Skip to content

Dependency original version is lost #37

@ntgussoni

Description

@ntgussoni

Hello guys,

I'm using this to parse a podfile, when creating the relation between a dependency and it's parent the original version (as it was stated in the podfile) gets lost.

{
 "foo@2.0.8" : [ ... ]
}
...
{
    "nodeId": "baz",
    "pkgId": "baz@2.0.1",
    "deps": [{ "nodeId": "foo" }, { "nodeId": "bar" }],
},

In the original podfile

- baz (2.0.1)
 - foo (>= 2.0.0)
 - bar (~> 1.0.0)

I'm interested not only on the actual resolved dependency but also in the original one. Is there any workaround or do I have to transverse the graph again myself to try to get it?

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