1. 08 Aug, 2020 1 commit
  2. 06 Aug, 2020 4 commits
  3. 31 Jul, 2020 1 commit
  4. 30 Jul, 2020 1 commit
  5. 24 Jul, 2020 1 commit
  6. 23 Jul, 2020 1 commit
  7. 16 Jul, 2020 4 commits
  8. 15 Jul, 2020 2 commits
    • Jacob Vosmaer (GitLab)'s avatar
      Merge branch '217392-read-references' into 'master' · ce696bcf
      Jacob Vosmaer (GitLab) authored
      Read and parse LSIF references
      
      See merge request gitlab-org/gitlab-workhorse!524
      ce696bcf
    • Patrick Bajao's avatar
      Read and parse LSIF references · 978671ce
      Patrick Bajao authored
      In order to be able to "Find references" of a given range or
      definition, we need to be able to read `references` items from
      the LSIF file.
      
      This will then be written to the JSON file for each range via
      `references` property.
      
      The property will look something like:
      
      ```
      "references": [
        {
          "path": "main.go#L7"
        }
      ]
      ```
      
      Each reference will be an object with `path` property. The `path`
      property will point to the exact line where it is being used.
      
      This is currently behind a feature flag (`code_navigation_references`)
      which will set `ProcessLsifReferences` header to `true` when
      enabled. If `false`, the `references` won't be read and generated.
      978671ce
  9. 14 Jul, 2020 3 commits
  10. 13 Jul, 2020 3 commits
  11. 03 Jul, 2020 3 commits
  12. 25 Jun, 2020 2 commits
  13. 17 Jun, 2020 4 commits
  14. 15 Jun, 2020 2 commits
  15. 11 Jun, 2020 4 commits
  16. 09 Jun, 2020 2 commits
  17. 04 Jun, 2020 2 commits