3.3 Integrations quality tracking issue
View options
- Truncate descriptions
Created by: lguychard
The source of truth for prioritization and what is being worked on are the browser-extension issues on the "Code nav" project board
The source of truth for what is done in 3.3 are the browser-extension issues on the 3.3 milestone
User story
@lguychard, @felixfbecker: Could someone provide a paragraph on why these specific set of issues, the benefits and who this will help. This helps greatly with the writing of the blog post.
Examples at #2025 (closed) and #2848 (closed)
Customer issues
- Improve "Enable on this site" #2770 (closed), PR: https://github.com/sourcegraph/sourcegraph/pull/2835
- Bugs: https://github.com/sourcegraph/sourcegraph/issues?q=is%3Aissue+label%3Abrowser-extension+milestone%3A3.3+label%3Abug
Technical Debt
- Remove dead code in the browser extension
- Activate stylelint for the browser extension https://github.com/sourcegraph/sourcegraph/issues/2517
-
Cleanup globals in
context.tsx
,context.ts
, rely onPlatformContext
when applicable, notably to differentiate in-page integration and browser extension. - Improve type safety of chrome.runtime communication, remove deprecated messages
-
Investigate removing global mutable
repoUrlCache
, or at the very least document its usage. - Clean up Phabricator backend code (legacy Promise code, copy-pasta) phabricator/backend.tsx
- Clean up injected script entry point (remove useless checks & steps, improve clarity) inject.tsx
-
Clean up
FileInfo
interface -base
-prefixed properties should be in a nested property and not optional #3107 (closed)
Stability & Polish
- Investigate most frequent Sentry exceptions
-
Improve reactive handling of DOM changes
-
use a single
MutationObserver
and make inject functions reactive to DOM changes by takingObservable<MutationRecord[]>
https://github.com/sourcegraph/sourcegraph/pull/2909, #3191
-
use a single
- Make styling more native to code host
-
Add unit tests with code host HTML DOM fixtures
- Mount getters
- DOM functions
Plan
Attack technical bugs and bugs by area:
-
Common/entry point (single mutation observer, error handling, backend logic, interfaces etc)
🏃 - Bitbucket
- GitHub & GitHub Enterprise
- Phabricator
- Gitlab