Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Feb 11 10:02
    hmemcpy closed #53
  • Oct 02 2020 10:23
    dredgy commented #178
  • Oct 02 2020 10:21
    FoggyFinder commented #178
  • Oct 02 2020 10:15
    dredgy opened #178
  • May 02 2020 14:14
    tebeco closed #122
  • Apr 10 2020 21:38
    gggggeorge closed #177
  • Apr 10 2020 21:37
    gggggeorge commented #177
  • Apr 10 2020 21:31
    gggggeorge opened #177
  • Jan 17 2020 16:54
    forki commented #176
  • Jan 17 2020 16:49
    jwosty commented #176
  • Jan 17 2020 07:28
    svdHero commented #176
  • Jan 16 2020 18:15
    forki commented #176
  • Jan 16 2020 18:01
    svdHero commented #176
  • Jan 16 2020 14:25
    FoggyFinder closed #173
  • Jan 16 2020 14:25
    FoggyFinder commented #173
  • Jan 16 2020 13:44
    isaacabraham commented #176
  • Jan 16 2020 13:41
    svdHero commented #176
  • Jan 16 2020 13:40
    svdHero commented #176
  • Jan 16 2020 09:41
    forki commented #176
  • Jan 16 2020 09:18
    svdHero commented #176
Jared Hester
@cloudRoutine
paket.ignore
Johan Larsson
@JohanLarsson
Think it would be more complicated and less flexible than a file
paket.ignore is better yes
Perhaps it would be nice to track number of local installs per package
Johan Larsson
@JohanLarsson
Would probably be a nice way to sort the default package list
Jared Hester
@cloudRoutine
i really need to take a look at the condition generation code in paket to see if i can consolidate it
so it makes large groups with all the references that share the same condition
Johan Larsson
@JohanLarsson
scrapping the ignore idea, was shit
doing favorites instead, simpler to use
Johan Larsson
@JohanLarsson
@forki no support for the query api in paket.core, should I add it there or keep it local in the UI thing?
Steffen Forkmann
@forki
what do you want with that?
we support package search
in public api
Johan Larsson
@JohanLarsson
for showing the list of packages when the search textbox is empty
that is the autocomplete search?
Steffen Forkmann
@forki
yes
Johan Larsson
@JohanLarsson
so you don't want it in core then, I was thinking it is about as good fit as the autocomplete
Steffen Forkmann
@forki
what can it do that autocomplete can't?
Johan Larsson
@JohanLarsson
  1. Empty query returns a list of the most downloaded packages on nuget. Nice when the search filter is empty.
  1. Autocomplete returns a list of package names, then info needs to be queried for each package. Query does it in one roundtrip
I'll add it to the ui thing, np.
Steffen Forkmann
@forki
No it would be OK to add to core. But issue is that only nuget.org implements that. So it's tricky
Johan Larsson
@JohanLarsson
Yeah, I'll change to proj ref to paket.core in the fork and prototype
and see if it becomes a thing
Johan Larsson
@JohanLarsson
Animation.gif
Maybe too subtle
Johan Larsson
@JohanLarsson
Animation.gif
Not very important, easy to move*
*Until released, after that not very nice to move.
Christian Fiebrig
@Stift
I like it
Steffen Forkmann
@forki
what is this?
Johan Larsson
@JohanLarsson
For the UI thing, you can mark packages as favorites.
Then when the search is empty we list favorite packages first and concat nuget search for empty packages.
I'm trying to write the UI clsoe to what nuget looks like and revealing some extra features in subtle ways.
Just fishing for some review of the ux.
Petter Vegsund Brodin
@g2petter

Imagine you have the following setup: a solution with 3 projects, A, B and C

A and B are in the same folder along with the solution file, paket.exe and paket.dependencies
C originates in another solution somewhere else on disk, which has its own paket.exe and paket.dependencies

I know this isn't an ideal setup, but for now it's a necessary evil.

The question is: how does Paket.VisualStudio decide which paket.exe file to use? Is it tied to the solution file, or is there a possibility that it can end up choosing the one from project C?

Igal Tabachnik
@hmemcpy
@forki should I only update the FAKE package, or just let it update all dependencies?
Steffen Forkmann
@forki
Update all the things
Igal Tabachnik
@hmemcpy
:thumbsup:
Igal Tabachnik
@hmemcpy
@forki can you give appveyor a kick again?
Steffen Forkmann
@forki
not possible
it's in queue and stuck
Igal Tabachnik
@hmemcpy
maybe ask @appveyor?
Igal Tabachnik
@hmemcpy
@forki I finally got it!
I just uploaded a broken vsix to my own account, and sure enough, I got the same message
blob
but then I fixed it properly (using an MS nuget package, of course)
and now it uploads fine :D
so one last pr!