Sorting the code search results by date has often been my only guide in a breadth-first search, to find out how to use an API in a recent state of the ecosystem, that I am working with.
I am working with .NET and .NET has seen lots and lots of changes in the past years. I often have to see the usage of a library in the current form of the .NET ecosystem, instead of say, an outdated .NET Framework project from 5 years ago.
Is there any equivalent for doing such a search in the new Code Search?
We want to do it right if we do implement it, but I can't promise anything concretely. It's not trivial, unfortunately.
Sorting the code search results by date has often been my only guide in a breadth-first search, to find out how to use an API in a recent state of the ecosystem, that I am working with.
I am working with .NET and .NET has seen lots and lots of changes in the past years. I often have to see the usage of a library in the current form of the .NET ecosystem, instead of say, an outdated .NET Framework project from 5 years ago.
Is there any equivalent for doing such a search in the new Code Search?
maybe lower standards would help - what does doing it not-quite-right-but-in-one-week look like? can mitigate by setting expectations accordingly