return a object instead of a string

[staabm]

in our use-case it would be more helpfull to have a value object returned from the api on which values (name, version, reference) could be obtained separately instead of a string.

would this be something we can agree on?

[Ocramius]

I'd rather keep this package extremely minimal: defining what a version looks like is not trivial (from what I saw in maintaining roave/security-advisories), so I'd rather defer this to @nikolaposa's work instead, and not have my own opinionated value types.

[staabm]

so I'd rather defer this to @nikolaposa's work instead, and not have my own opinionated value types.

does this mean there is another package with a more complex api (I am not aware of )?

[Ocramius]

Correct: this package only focuses on providing the raw information.

On Thu, 7 Feb 2019, 14:28 Markus Staab <notifications@github.com wrote:

so I'd rather defer this to @nikolaposa https://github.com/nikolaposa's work instead, and not have my own opinionated value types.

does this mean there is another package with a more complex api?

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/Ocramius/PackageVersions/issues/77#issuecomment-461441248, or mute the thread https://github.com/notifications/unsubscribe-auth/AAJakH6ZXkDJTGf1Vmrjq1zRYqOyNEVwks5vLDgBgaJpZM4anZAX .

[nikolaposa]

so I'd rather defer this to @nikolaposa's work instead, and not have my own opinionated value types.

does this mean there is another package with a more complex api (I am not aware of )?

@staabm This one for example: https://github.com/nikolaposa/version