unisonweb/unison

missing `find` results?

Open

#1,239 opened on Feb 14, 2020

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Haskell (304 forks)batch import
help wanted

Repository metrics

Stars
 (6,624 stars)
PR merge metrics
 (Avg merge 12d 19h) (6 merged PRs in 30d)

Description

What is going on here?

.> find Some

  1. base.Optional.Some : a -> Optional a
  
.> find builtin.Optional

  1. type builtin.Optional a
  2. builtin.Optional.None : Optional a
  3. builtin.Optional.Some : a -> Optional a
  

.> find Some

  1. base.Optional.Some : a -> Optional a

Where are the rest of the Some? Where's builtin.Optional.Some, which I was just shown?

.> find builtin.Optional.Some

  1. builtin.Optional.Some : a -> Optional a
  
.> find base.Optional.Some

  1. prs.puffnfresh.base.Optional.Some : a -> Optional a

Wait what? Where's the base.Optional.Some that I was shown earlier? Also it's probably not just prs.puffnfresh.base, right? Don't head and merged have an Optional.Some?

.> find .base.Optional.Some

  1. prs.puffnfresh.base.Optional.Some : a -> Optional a
  
.> ls prs.puffnfresh.head.Optional 

  1. None      (Optional a)
  2. Some      (a -> Optional a)
  3. flatMap   ((a ->{𝕖} Optional b) -> Optional a ->{𝕖} Optional b)
  4. map       ((a ->{𝕖} b) -> Optional a ->{𝕖} Optional b)
  5. map2      ((a ->{𝕖} b ->{𝕖} c) -> Optional a -> Optional b ->{𝕖} Optional c)
  6. orDefault (a -> Optional a -> a)
  7. orElse    (Optional a -> Optional a -> Optional a)

.>

Contributor guide

Research direction
Investigate the implementation of the `find` command in the Unison CLI. Focus on how the search results are filtered or aggregated when partial module names are used. Consider how namespaces like `base.Optional` and `builtin.Optional` are resolved, and why `find Some` might only show one result despite multiple matches. Look at the code that handles search queries and the namespace hierarchy.
Tech stack
None
Domain
cli
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70