-
Notifications
You must be signed in to change notification settings - Fork 519
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
paket outdated goes off on a useless search when using the v3 api #1242
Comments
|
@xavierzwirtz ideas? |
|
I can reproduce with "paket update" |
|
I've seen it do that as well, not entirely sure what's causing it yet. It always resolves to the same packages as the v2 api, but it takes it awhile. |
|
but https://www.nuget.org/packages/SnmpSharpNet/0.9.3 shows it as listed |
|
|
vs. FAKE: |
|
so it seems "listed" is not always set. And when it's not set we should assume "true". @xavierzwirtz what do you think about it? Can you do a PR? |
|
/cc @maartenba do you know why the listed property is sometimes not set. Even when nuget.org shows the package as listed? |
|
Listed by default indeed, we have had a version of the schema that excluded the trues for a bit in the first months of the year. |
|
Isn't that a Json "violation" in some sense? why didn't you use "unlisted" with default false? Just kidding. ;-) we can fix that in paket. BTW: can you comment on #1230 (comment)? Please only that single comment. I don't want to reraise the whole pointless discussion on that thread. But this comment seems related. |
|
If I find a few hours I want to document the API a bit better (and hopefully officially as well), should help a lot imo. On that thread, no idea on the reasons there... |
|
Documentation would be great. Had to black box most of this implementation with fiddler. |
|
Preaching to the choir :-) I hear you. |
|
You want me to submit a PR to fix this @forki? |
|
Yes would be great
|
|
Thanks everyone! @deapsquatter looks like our paket anomaly has been solved 😄 |

dependencies:
Output:
If I remove the v3 source
The text was updated successfully, but these errors were encountered: