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

Code search UX #2081

Open
sqs opened this Issue Jan 30, 2019 · 3 comments

Comments

Projects
None yet
5 participants
@sqs
Copy link
Member

sqs commented Jan 30, 2019

NOTE: This issue description has not been updated yet for the 3.2 release cycle.

Code search, along with code navigation, is one of the 2 main features of Sourcegraph. We have a growing backlog of issues and feature requests that should be addressed before next release cycle when we can hopefully start on the bigger features of subquery search (#1005) and invoking search extensions on the backend.

The priorities are improving the search experience for new users and fixing bugs.

Plan

Issues labeled search

  • #2125
  • #652
  • #1234
  • #1624 (do initial investigation; can defer if solution becomes involved)
  • The rest of the search issues in the milestone can be prioritized after the above issues are done.

Test/review plan

  • Code reviewer: project team
  • Tester: project team

@sqs sqs added this to the 3.1 milestone Jan 30, 2019

@sqs sqs referenced this issue Jan 31, 2019

Open

Sub-query searches #1005

4 of 10 tasks complete
@keegancsmith

This comment has been minimized.

Copy link
Member

keegancsmith commented Feb 1, 2019

Cool, so the plan is to address some search issues / polish, then finish off sub-query search. A comprehensive list of changes will be useful for when planning finishing off sub-query search, in case a change/feature/fix should be "ported" to sub-query search.

@sqs

This comment has been minimized.

Copy link
Member Author

sqs commented Feb 3, 2019

Cool, so the plan is to address some search issues / polish, then finish off sub-query search.

Yeah, except sub-query search (and invoking search extensions) definitely won't be worked on directly in this release cycle. (In case anyone reads your sentence above and thinks otherwise.)

@nicksnyder

This comment has been minimized.

Copy link
Member

nicksnyder commented Feb 19, 2019

Most of these are still open so I am moving this to 3.2. We will discuss in the kickoff on Wednesday.

@nicksnyder nicksnyder modified the milestones: 3.1, 3.2 Feb 19, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment