This document explains how the current code is structured and it also
hints at what changes are we planning to do to the extension structure
in the near future.

docs: add architecture.md

See merge request gitlab-org/gitlab-vscode-extension!187

Felix Haase authored Feb 23, 2021 and Tomas Vik (OOO back on 2026-08-31) committed Feb 23, 2021

A simple implementation of the git.clone command for the configured
instances.
It also includes a credential provider that can clone the repository
without user input using the access token

See merge request gitlab-org/gitlab-vscode-extension!172

Relates to #222

Implement git clone command

See merge request !172

This is a snippet from a book Effective TypeScript:

WARNING
The examples in this item prefix type names with I or T solely to
indicate how they were defined. You should not do this in your code!
Prefixing interface types with I is common in C#, and this convention
made some inroads in the early days of TypeScript. But it is considered
bad style today because it’s unnecessary, adds little value, and is not
consistently followed in the standard libraries.

We migrated to TS and introduced new concepts since the last update.

The testing strategy has been written before we started
writing tests. Now after months of writign tests, lot of the
processes changed.

Developer documentation review and update.

See merge request !188

refactor: use union types to better represent discussions

See merge request gitlab-org/gitlab-vscode-extension!189

chore(ci variables): update the ci_variables.json

See merge request gitlab-org/gitlab-vscode-extension!191

The testing responsibility is now strictly divided. The tree_view test
is responsible for validating querying lists of issues/MRs and
showing these lists as items in the tree_view.

The new mr_review test is responsible for all interactions with the MR
item, including showing changed files when clicked, fetching
discussions and any future review functionality.

This commit splits the "shows project merge requests assigned to me with
changed files" test in two and all other tests just moved around
unchanged.

The GitLabComment is going to be responsible for all comment-related
functionality like editing, deleting and reacting.

All logic related to creating vscode.CommentThread and
setting the correct properties has been extracted to one class.

This class will be responsible for resolving threads in the future.

refactor: introduce separate classes for threads and comments

See merge request gitlab-org/gitlab-vscode-extension!190

feat(mr review): display whether discussion is resolved or not

See merge request !193

feat(mr review): resolving and unresolving discussions

See merge request !194

feat(mr review): deleting comments on MR diff

See merge request !195

Convert typescript integration tests to unit tests

See merge request !192