@codingame/monaco-editor-wrapper 26.0.0 → 28.0.0

package/dist/assets/{ms-vscode.cpptools-1.31.0.vsix → ms-vscode.cpptools-1.32.1.vsix}/package.nls.ko.json

@@ -180,7 +180,7 @@
 	"c_cpp.configuration.intelliSenseEngine.default.description": "별도의 IntelliSense 프로세스를 통해 컨텍스트 인식 결과를 제공합니다.",
 	"c_cpp.configuration.intelliSenseEngine.tagParser.description": "\"유사\" 결과를 제공합니다. 컨텍스트를 인식하지 않는 결과입니다.",
 	"c_cpp.configuration.intelliSenseEngine.disabled.description": "C/C++ 언어 서비스 기능을 해제합니다.",
-	"c_cpp.configuration.autocomplete.markdownDescription": "자동 완성 공급자를 제어합니다. `disabled`에서 단어 기반 완성을 원할 경우 `\"[cpp]\": {\"editor.wordBasedSuggestions\": <value>}`를 설정해야 합니다(`c`와 `cuda-cpp` 언어도 동일).",
+	"c_cpp.configuration.autocomplete.markdownDescription": "자동 완성 공급자를 제어합니다. `disabled`에서 단어 기반 완성을 원할 경우 `\"[cpp]\": {\"editor.wordBasedSuggestions\": <값>}`를 설정해야 합니다(`c`와 `cuda-cpp` 언어도 동일).",
 	"c_cpp.configuration.autocomplete.default.description": "활성 IntelliSense 엔진을 사용합니다.",
 	"c_cpp.configuration.autocomplete.disabled.description": "Visual Studio Code에서 제공하는 단어 기반 완성을 사용합니다.",
 	"c_cpp.configuration.errorSquiggles.description": "IntelliSense 엔진에서 감지한 의심스러운 컴파일 오류를 편집기에 다시 보고할지 여부를 제어합니다. 또한 포함 사항을 찾을 수 없는 경우 코드 분석 경고가 보고되는지 여부를 제어합니다. 이 설정은 태그 파서 엔진에서 무시됩니다.",
@@ -205,6 +205,7 @@
 	"c_cpp.configuration.preferredPathSeparator.markdownDescription": "생성된 사용자 경로의 경로 구분 기호로 사용되는 문자입니다.",
 	"c_cpp.configuration.simplifyStructuredComments.markdownDescription": "`true`인 경우 가리키기 및 자동 완성 도구 설명에 구조적 주석의 특정 레이블만 표시됩니다. 그렇지 않으면 모든 주석이 표시됩니다.",
 	"c_cpp.configuration.doxygen.generateOnType.description": "선택한 주석 스타일을 입력한 후 Doxygen 주석을 자동으로 삽입할지 여부를 제어합니다.",
+	"c_cpp.configuration.doxygen.generateOnCodeAction.description": "Doxygen 주석을 생성하는 코드 작업을 사용할지 여부를 제어합니다.",
 	"c_cpp.configuration.doxygen.generatedStyle.description": "Doxygen 주석의 시작 줄로 사용되는 문자 문자열입니다.",
 	"c_cpp.configuration.doxygen.sectionTags.description": "'구조적 설명 단순화' 설정이 활성화된 경우 도구 설명 영역에서 마우스를 가져가면 표시할 Doxygen 섹션 태그를 선택합니다. ",
 	"c_cpp.configuration.commentContinuationPatterns.items.anyof.string.markdownDescription": "여러 줄 또는 한 줄 주석 블록을 시작하는 패턴입니다. 기본적으로 여러 줄 주석 블록의 계속 패턴은 ` * `로 설정되고, 한 줄 주석 블록의 경우 이 문자열로 설정됩니다.",
@@ -326,13 +327,8 @@
 	"c_cpp.debuggers.avoidWindowsConsoleRedirection.description": "True이면 통합 터미널 지원에 필요한 디버기 콘솔 리디렉션을 사용하지 않도록 설정합니다.",
 	"c_cpp.debuggers.sourceFileMap.markdownDescription": "디버그 엔진에 전달되는 선택적 소스 파일 매핑입니다. 예: `{ \"<원래 소스 경로>\": \"<현재 소스 경로>\" }`.",
 	"c_cpp.debuggers.processId.anyOf.markdownDescription": "디버거를 연결할 선택적 프로세스 ID입니다. `${command:pickProcess}`를 사용하여 연결할 로컬 실행 프로세스 목록을 가져옵니다. 일부 플랫폼에서는 프로세스에 연결하기 위해 관리자 권한이 필요합니다.",
-	"c_cpp.debuggers.program.attach.markdownDescription": {
-		"message": "Full path to the program executable. The debugger will search for a running process matching this executable path and attach to it. If multiple processes match, a selection prompt will be shown. This field is required to load debug symbols for the attached process.",
-		"comment": [
-			"{Locked=\"`program`\"}"
-		]
-	},
-	"c_cpp.debuggers.symbolSearchPath.description": "기호(pdb) 파일 검색에 사용할 디렉터리의 세미콜론으로 구분된 목록입니다(예: \"c:\\dir1;c:\\dir2\").",
+	"c_cpp.debuggers.program.attach.markdownDescription": "프로그램 실행 파일의 전체 경로입니다. 디버거는 이 실행 파일 경로와 일치하는 실행 중인 프로세스를 찾아 연결합니다. 여러 프로세스가 일치하는 경우 선택 프롬프트가 나타납니다. 이 필드는 연결된 프로세스의 디버그 기호를 로드하는 데 필요합니다.",
+	"c_cpp.debuggers.symbolSearchPath.description": "기호(pdb 또는 .so) 파일 검색에 사용할 디렉터리의 세미콜론으로 구분된 목록입니다. 예: \"c:\\dir1;c:\\dir2\".",
 	"c_cpp.debuggers.dumpPath.description": "지정된 프로그램에 대한 코어 덤프 파일의 선택적 전체 경로입니다(예: \"c:\\temp\\app.dmp\"). 기본값은 null입니다.",
 	"c_cpp.debuggers.enableDebugHeap.description": "False이면 디버그 힙이 사용하지 않도록 설정된 상태로 프로세스가 시작됩니다. 이렇게 하면 환경 변수 '_NO_DEBUG_HEAP'이 '1'로 설정됩니다.",
 	"c_cpp.debuggers.symbolLoadInfo.description": "기호 로드를 명시적으로 제어합니다.",

package/dist/assets/{ms-vscode.cpptools-1.31.0.vsix → ms-vscode.cpptools-1.32.1.vsix}/package.nls.pl.json

@@ -205,6 +205,7 @@
 	"c_cpp.configuration.preferredPathSeparator.markdownDescription": "Znak używany jako separator ścieżek dla wygenerowanych ścieżek użytkowników.",
 	"c_cpp.configuration.simplifyStructuredComments.markdownDescription": "W przypadku wartości `true` etykietki narzędzi najechania kursorem oraz automatycznego uzupełniania będą wyświetlać tylko określone etykiety komentarzy ze strukturą. W przeciwnym razie wyświetlane będą wszystkie komentarze.",
 	"c_cpp.configuration.doxygen.generateOnType.description": "Określa, czy komentarz Doxygen ma być wstawiany automatycznie po wpisaniu wybranego stylu komentarza.",
+	"c_cpp.configuration.doxygen.generateOnCodeAction.description": "Określa, czy akcja kodu w celu wygenerowania komentarza Doxygen jest włączona.",
 	"c_cpp.configuration.doxygen.generatedStyle.description": "Ciąg znaków używany jako wiersz początkowy komentarza Doxygen.",
 	"c_cpp.configuration.doxygen.sectionTags.description": "Wybierz tagi sekcji Doxygen, które mają być wyświetlane po zatrzymaniu wskaźnika myszy w obszarze etykietki narzędzia po włączeniu ustawienia „Uprość komentarze strukturalne”. ",
 	"c_cpp.configuration.commentContinuationPatterns.items.anyof.string.markdownDescription": "Wzorzec, który rozpoczyna wielowierszowy lub jednowierszowy blok komentarza. Wartość domyślna wzorca kontynuacji to ` * ` w przypadku wielowierszowych bloków komentarzy lub ten ciąg w przypadku jednowierszowych bloków komentarza.",
@@ -326,13 +327,8 @@
 	"c_cpp.debuggers.avoidWindowsConsoleRedirection.description": "Jeśli wartość to true, wyłącza przekierowywanie konsoli debugowanego obiektu, które jest wymagane do obsługi zintegrowanego terminalu.",
 	"c_cpp.debuggers.sourceFileMap.markdownDescription": "Opcjonalne mapowania plików źródłowych przekazane do silnika debugowania. Przykład: `{ \"<początkowa ścieżka źródłowa>\": \"<bieżąca ścieżka źródłowa>\" }`.",
 	"c_cpp.debuggers.processId.anyOf.markdownDescription": "Opcjonalny identyfikator procesu, do którego ma zostać dołączony debuger. Użyj polecenia `${command:pickProcess}`, aby uzyskać listę uruchomionych lokalnie procesów, do których można dołączyć. Pamiętaj, że niektóre platformy wymagają uprawnień administratora, aby dołączyć je do procesu.",
-	"c_cpp.debuggers.program.attach.markdownDescription": {
-		"message": "Full path to the program executable. The debugger will search for a running process matching this executable path and attach to it. If multiple processes match, a selection prompt will be shown. This field is required to load debug symbols for the attached process.",
-		"comment": [
-			"{Locked=\"`program`\"}"
-		]
-	},
-	"c_cpp.debuggers.symbolSearchPath.description": "Rozdzielana średnikami lista katalogów, w których mają być wyszukiwanie pliki symboli (PDB). Przykład: „c:\\dir1;c:\\dir2”.",
+	"c_cpp.debuggers.program.attach.markdownDescription": "Pełna ścieżka do pliku wykonywalnego programu. Debuger wyszuka uruchomiony proces zgodny z tą ścieżką wykonywalną i dołączy do niego. Jeśli wiele procesów jest zgodnych, zostanie wyświetlony monit o zaznaczenie. To pole jest wymagane do załadowania symboli debugowania dla dołączonego procesu.",
+	"c_cpp.debuggers.symbolSearchPath.description": "Rozdzielana średnikami lista katalogów do wyszukiwania plików symboli (tj. pdb lub .so). Przykład: „c:\\dir1;c:\\dir2”.",
 	"c_cpp.debuggers.dumpPath.description": "Opcjonalna pełna ścieżka do pliku zrzutu dla określonego programu. Przykład: „c:\\temp\\app.dmp”. Wartość domyślna to null.",
 	"c_cpp.debuggers.enableDebugHeap.description": "W przypadku wartości false proces zostanie uruchomiony z wyłączoną stertą debugowania. Spowoduje to ustawienie zmiennej środowiskowej „_NO_DEBUG_HEAP” na wartość „1”.",
 	"c_cpp.debuggers.symbolLoadInfo.description": "Jawna kontrola ładowania symboli.",

package/dist/assets/{ms-vscode.cpptools-1.31.0.vsix → ms-vscode.cpptools-1.32.1.vsix}/package.nls.pt-br.json

@@ -205,6 +205,7 @@
 	"c_cpp.configuration.preferredPathSeparator.markdownDescription": "O caractere usado como separador de caminho para caminhos de usuário gerados.",
 	"c_cpp.configuration.simplifyStructuredComments.markdownDescription": "Se for `true`, as dicas de passar o mouse e autocompletar exibirão apenas alguns rótulos de comentários estruturados. Caso contrário, todos os comentários serão exibidos.",
 	"c_cpp.configuration.doxygen.generateOnType.description": "Controle se o comentário Doxygen deve ser inserido automaticamente depois de digitar o estilo de comentário escolhido.",
+	"c_cpp.configuration.doxygen.generateOnCodeAction.description": "Controla se a ação de código para gerar um comentário do Doxygen está habilitada.",
 	"c_cpp.configuration.doxygen.generatedStyle.description": "A cadeia de caracteres usada como a linha inicial do comentário Doxygen.",
 	"c_cpp.configuration.doxygen.sectionTags.description": "Selecione as tags de seção do Doxygen que você quer exibir ao focalizar na área de dica de ferramenta quando a configuração `Simplificar Comentários Estruturados` estiver habilitada. ",
 	"c_cpp.configuration.commentContinuationPatterns.items.anyof.string.markdownDescription": "O padrão que inicia um bloco de comentário de várias linhas ou de uma linha. O padrão de continuação é `*` para blocos de comentários de várias linhas ou esta cadeia de caracteres para blocos de comentários de uma única linha.",
@@ -326,13 +327,8 @@
 	"c_cpp.debuggers.avoidWindowsConsoleRedirection.description": "Se for true, desabilitará o redirecionamento do console do depurador requerido para o suporte do Terminal Integrado.",
 	"c_cpp.debuggers.sourceFileMap.markdownDescription": "Mapeamentos opcionais de arquivo de origem passados para o mecanismo de depuração. Exemplo: `{ \"<caminho original do arquivo de origem>\": \"<caminho atual do arquivo de origem>\" }`.",
 	"c_cpp.debuggers.processId.anyOf.markdownDescription": "ID do processo opcional ao qual anexar o depurador. Use `${command:pickProcess}` para obter uma lista de processos locais em execução aos quais anexar. Observe que algumas plataformas exigem privilégios de administrador para anexação a um processo.",
-	"c_cpp.debuggers.program.attach.markdownDescription": {
-		"message": "Full path to the program executable. The debugger will search for a running process matching this executable path and attach to it. If multiple processes match, a selection prompt will be shown. This field is required to load debug symbols for the attached process.",
-		"comment": [
-			"{Locked=\"`program`\"}"
-		]
-	},
-	"c_cpp.debuggers.symbolSearchPath.description": "Lista separada por ponto e vírgula de diretórios a serem usados para pesquisar arquivos de símbolo (ou seja, pdb). Exemplo: \"c:\\dir1;c:\\dir2\".",
+	"c_cpp.debuggers.program.attach.markdownDescription": "Caminho completo para o executável do programa. O depurador pesquisará um processo em execução que corresponda a esse caminho executável e anexará a ele. Se vários processos corresponderem, um prompt de seleção será mostrado. Esse campo é necessário para carregar símbolos de depuração para o processo anexado.",
+	"c_cpp.debuggers.symbolSearchPath.description": "Lista separada por ponto e vírgula de diretórios a serem usadas para pesquisar arquivos de símbolos (ou seja, pdb ou .so). Exemplo: \"c:\\dir1;c:\\dir2\".",
 	"c_cpp.debuggers.dumpPath.description": "Caminho completo opcional para um arquivo de despejo para o programa especificado. Exemplo: \"c:\\temp\\app.dmp\". Usa nulo como padrão.",
 	"c_cpp.debuggers.enableDebugHeap.description": "Se for false, o processo será iniciado com o heap de depuração desabilitado. Isso define a variável de ambiente '_NO_DEBUG_HEAP' como '1'.",
 	"c_cpp.debuggers.symbolLoadInfo.description": "Controle explícito do carregamento de símbolo.",

package/dist/assets/{ms-vscode.cpptools-1.31.0.vsix → ms-vscode.cpptools-1.32.1.vsix}/package.nls.ru.json

@@ -180,7 +180,7 @@
 	"c_cpp.configuration.intelliSenseEngine.default.description": "Предоставляет результаты, зависящие от контекста, с помощью отдельного процесса IntelliSense.",
 	"c_cpp.configuration.intelliSenseEngine.tagParser.description": "Предоставляет \"нечеткие\" результаты, не зависящие от контекста.",
 	"c_cpp.configuration.intelliSenseEngine.disabled.description": "Отключает компоненты службы языка C/C++.",
-	"c_cpp.configuration.autocomplete.markdownDescription": "Управляет поставщиком автозавершения. Если присвоено значение `disabled`, и вам требуется завершение по словам, также настройте `\"[cpp]\": {\"editor.wordBasedSuggestions\": <value>}` (и аналогично для языков `c` и `cuda-cpp`).",
+	"c_cpp.configuration.autocomplete.markdownDescription": "Управляет поставщиком автозавершения. Если присвоено значение `disabled`, и вам требуется завершение по словам, также настройте `\"[cpp]\": {\"editor.wordBasedSuggestions\": <значение>}` (и аналогично для языков `c` и `cuda-cpp`).",
 	"c_cpp.configuration.autocomplete.default.description": "Использует активную подсистему IntelliSense.",
 	"c_cpp.configuration.autocomplete.disabled.description": "Использует завершение на основе слов, предоставляемое Visual Studio Code.",
 	"c_cpp.configuration.errorSquiggles.description": "Определяет, будут ли обнаруженные подсистемой IntelliSense предполагаемые ошибки компиляции возвращены в редактор. Также определяет, будут ли отображаться предупреждения на этапе анализа кода, если не удается найти включаемые данные. Этот параметр игнорируется подсистемой синтаксического анализа тегов.",
@@ -205,6 +205,7 @@
 	"c_cpp.configuration.preferredPathSeparator.markdownDescription": "Символ, используемый в качестве разделителя путей для созданных путей пользователей.",
 	"c_cpp.configuration.simplifyStructuredComments.markdownDescription": "Если выбрано значение `true`, в подсказках при наведении указателя и автозавершении будут отображаться только определенные метки со структурированными комментариями. В противном случае отображаются все комментарии.",
 	"c_cpp.configuration.doxygen.generateOnType.description": "Определяет, следует ли автоматически вставлять комментарий Doxygen после ввода выбранного стиля комментария.",
+	"c_cpp.configuration.doxygen.generateOnCodeAction.description": "Управляет включением действия кода для создания комментария Doxygen.",
 	"c_cpp.configuration.doxygen.generatedStyle.description": "Строка символов, используемая в качестве начальной строки комментария Doxygen.",
 	"c_cpp.configuration.doxygen.sectionTags.description": "Выберите теги раздела Doxygen, которые должны отображаться при наведении курсора на область подсказок, если включен параметр \"Упростить структурированные комментарии\".",
 	"c_cpp.configuration.commentContinuationPatterns.items.anyof.string.markdownDescription": "Шаблон, который начинается с многострочного или однострочного примечания. Шаблон продолжения по умолчанию имеет значение ` * ` для многострочных примечаний или соответствует этой строке для однострочных примечаний.",
@@ -326,13 +327,8 @@
 	"c_cpp.debuggers.avoidWindowsConsoleRedirection.description": "Если задано значение true, отключается перенаправление консоли отлаживаемого объекта, необходимое для поддержки встроенного терминала.",
 	"c_cpp.debuggers.sourceFileMap.markdownDescription": "Необязательные сопоставления исходных файлов, передаваемые подсистеме отладки. Пример: `{ \"<первоначальный путь к источнику>\": \"<текущий путь к источнику>\" }`.",
 	"c_cpp.debuggers.processId.anyOf.markdownDescription": "Необязательный идентификатор процесса, к которому требуется подключить отладчик. Используйте `${command:pickProcess}`, чтобы получить список локальных запущенных процессов для подключения. Обратите внимание, что для подключения к процессам на некоторых платформах требуются права администратора.",
-	"c_cpp.debuggers.program.attach.markdownDescription": {
-		"message": "Full path to the program executable. The debugger will search for a running process matching this executable path and attach to it. If multiple processes match, a selection prompt will be shown. This field is required to load debug symbols for the attached process.",
-		"comment": [
-			"{Locked=\"`program`\"}"
-		]
-	},
-	"c_cpp.debuggers.symbolSearchPath.description": "Список каталогов, разделенных точкой с запятой, который следует использовать для поиска файлов символов (таких как PDB). Пример: \"c:\\каталог_1;c:\\каталог_2\".",
+	"c_cpp.debuggers.program.attach.markdownDescription": "Полный путь к исполняемому файлу program. Отладчик будет искать запущенный процесс, совпадающий с путем этого исполняемого файла, и подключаться к нему. Если процессов несколько, появится запрос выбора. Это поле обязательно с целью загрузки символов отладки для подключенного процесса.",
+	"c_cpp.debuggers.symbolSearchPath.description": "Список каталогов, разделенных точкой с запятой, который следует использовать для поиска файлов символов (таких как PDB или SO). Пример: \"c:\\каталог_1;c:\\каталог_2\".",
 	"c_cpp.debuggers.dumpPath.description": "Необязательный полный путь к основному файлу дампа для указанной программы. Пример: \"c:\\temp\\app.dmp\". Значение по умолчанию: null.",
 	"c_cpp.debuggers.enableDebugHeap.description": "Если задано значение false, процесс будет запущен с отключенной кучей отладки. При этом для переменной среды \"_NO_DEBUG_HEAP\" устанавливается значение \"1\".",
 	"c_cpp.debuggers.symbolLoadInfo.description": "Явный контроль загрузки символов.",

package/dist/assets/{ms-vscode.cpptools-1.31.0.vsix → ms-vscode.cpptools-1.32.1.vsix}/package.nls.tr.json

@@ -180,7 +180,7 @@
 	"c_cpp.configuration.intelliSenseEngine.default.description": "Ayrı bir IntelliSense işlemi aracılığıyla bağlama duyarlı sonuçlar sağlar.",
 	"c_cpp.configuration.intelliSenseEngine.tagParser.description": "Bağlama duyarlı olmayan \"belirsiz\" sonuçlar sağlar.",
 	"c_cpp.configuration.intelliSenseEngine.disabled.description": "C/C++ dil hizmeti özelliklerini kapatır.",
-	"c_cpp.configuration.autocomplete.markdownDescription": "Otomatik tamamlama sağlayıcısını kontrol eder. `disabled` ise ve sözcük tabanlı tamamlama istiyorsanız, aynı zamanda `\"[cpp]\": {\"editor.wordBasedSuggestions\": <value>}` (ve aynı şekilde `c` ve `cuda-cpp` dilleri için) ayarını da belirlemeniz gerekir.",
+	"c_cpp.configuration.autocomplete.markdownDescription": "Otomatik tamamlama sağlayıcısını kontrol eder. `disabled` ise ve sözcük tabanlı tamamlama istiyorsanız, aynı zamanda `\"[cpp]\": {\"editor.wordBasedSuggestions\": <değer>}` (ve aynı şekilde `c` ve `cuda-cpp` dilleri için) ayarını da belirlemeniz gerekir.",
 	"c_cpp.configuration.autocomplete.default.description": "Etkin IntelliSense altyapısını kullanır.",
 	"c_cpp.configuration.autocomplete.disabled.description": "Visual Studio Code tarafından sağlanan sözcük tabanlı tamamlamayı kullanır.",
 	"c_cpp.configuration.errorSquiggles.description": "IntelliSense altyapısı tarafından algılanan şüpheli derleme hatalarının düzenleyiciye geri rapor edilip edilmeyeceğini kontrol eder. Ayrıca, içermeler bulunamazsa kod analizi uyarılarının raporlanıp raporlanmayacağını da kontrol eder. Bu ayar, Etiket Ayrıştırıcı motoru tarafından yok sayılır.",
@@ -205,6 +205,7 @@
 	"c_cpp.configuration.preferredPathSeparator.markdownDescription": "Oluşturulan kullanıcı yolları için yol ayırıcı olarak kullanılan karakter.",
 	"c_cpp.configuration.simplifyStructuredComments.markdownDescription": "`true` ise, üzerine gelme ve otomatik tamamlama araç ipuçları, yapılandırılmış açıklamaların yalnızca belirli etiketlerini görüntüler. Aksi halde tüm açıklamalar görüntülenir.",
 	"c_cpp.configuration.doxygen.generateOnType.description": "Seçilen açıklama stilini girdikten sonra Doxygen açıklamasının otomatik olarak eklenip eklenmeyeceğini kontrol eder.",
+	"c_cpp.configuration.doxygen.generateOnCodeAction.description": "Doxygen açıklaması oluşturma kod eyleminin etkin olup olmadığını denetler.",
 	"c_cpp.configuration.doxygen.generatedStyle.description": "Doxygen açıklamasının başlangıç satırı olarak kullanılan karakter dizesi.",
 	"c_cpp.configuration.doxygen.sectionTags.description": "\"Yapılandırılmış Yorumları Basitleştir\" ayarı etkinleştirildiğinde araç ipucu alanında fareyle üzerine gelindiğinde görünmesini istediğiniz Doxygen bölümü etiketlerini seçin. ",
 	"c_cpp.configuration.commentContinuationPatterns.items.anyof.string.markdownDescription": "Çok satırlı veya tek satırlı açıklama bloğu başlatan desen. Devam deseni, çok satırlı açıklama blokları için varsayılan olarak ` * ` değerini veya tek satırlı açıklama blokları için bu dize değerini alır.",
@@ -326,13 +327,8 @@
 	"c_cpp.debuggers.avoidWindowsConsoleRedirection.description": "Değer true ise, Tümleşik Terminal desteği için gerekli olan hata ayıklanan işlem konsol yeniden yönlendirmesini devre dışı bırakır.",
 	"c_cpp.debuggers.sourceFileMap.markdownDescription": "Hata ayıklama altyapısına geçirilen isteğe bağlı kaynak dosya eşlemeleri. Örnek: `{ \"<orijinal kaynak yolu>\": \"<geçerli kaynak yolu>\" }`.",
 	"c_cpp.debuggers.processId.anyOf.markdownDescription": "Hata ayıklayıcının ekleneceği isteğe bağlı işlem kimliği. Eklenilecek yerel çalışan işlemlerin bir listesini almak için `${command:pickProcess}` kullanın. Bazı platformların bir işleme ekleme yapmak için yönetici ayrıcalıkları gerektirdiğini unutmayın.",
-	"c_cpp.debuggers.program.attach.markdownDescription": {
-		"message": "Full path to the program executable. The debugger will search for a running process matching this executable path and attach to it. If multiple processes match, a selection prompt will be shown. This field is required to load debug symbols for the attached process.",
-		"comment": [
-			"{Locked=\"`program`\"}"
-		]
-	},
-	"c_cpp.debuggers.symbolSearchPath.description": "Sembol (yani pdb) dosyalarını aramak için kullanılacak, noktalı virgülle ayrılmış dizinlerin listesi. Örnek: \"c:\\dizin1;c:\\dizin2\".",
+	"c_cpp.debuggers.program.attach.markdownDescription": "Programın yürütülebilir dosyasının tam yolu. Hata ayıklayıcı, bu yürütülebilir dosya yoluyla eşleşen çalışan bir işlemi arayacak ve ona eklenecek. Birden çok çalışan işlem eşleşiyorsa bir seçim istemi gösterilecek. Ekli işlem için hata ayıklama sembollerini yüklerken bu alan gereklidir.",
+	"c_cpp.debuggers.symbolSearchPath.description": "Sembol (yani pdb veya .so) dosyalarını aramak için kullanılacak, noktalı virgülle ayrılmış dizinlerin listesi. Örnek: \"c:\\dizin1;c:\\dizin2\".",
 	"c_cpp.debuggers.dumpPath.description": "Belirtilen program için döküm dosyasının isteğe bağlı tam yolu. Örnek: \"c:\\temp\\app.dmp\". Varsayılan olarak null değerini alır.",
 	"c_cpp.debuggers.enableDebugHeap.description": "Değer false ise, işlem hata ayıklama yığını devre dışı bırakılarak başlatılır. Bu işlem '_NO_DEBUG_HEAP' ortam değişkenini '1' olarak ayarlar.",
 	"c_cpp.debuggers.symbolLoadInfo.description": "Sembol yüklemesinin açık denetimi.",

package/dist/assets/{ms-vscode.cpptools-1.31.0.vsix → ms-vscode.cpptools-1.32.1.vsix}/package.nls.zh-cn.json

@@ -180,7 +180,7 @@
 	"c_cpp.configuration.intelliSenseEngine.default.description": "通过单独的 IntelliSense 流程提供上下文感知结果。",
 	"c_cpp.configuration.intelliSenseEngine.tagParser.description": "提供非上下文感知的“模糊”结果。",
 	"c_cpp.configuration.intelliSenseEngine.disabled.description": "关闭 C/C++ 语言服务功能。",
-	"c_cpp.configuration.autocomplete.markdownDescription": "控制自动完成提供程序。如果 `disabled`，且你想要基于字词的补全功能，则还需要设置 `\"[cpp]\": {\"editor.wordBasedSuggestions\": <value>}` (`c` 和 `cuda-cpp` 语言也类似)。",
+	"c_cpp.configuration.autocomplete.markdownDescription": "控制自动完成提供程序。如果值为 `disabled`，并且你想要基于字词的补全功能，则还需要设置 `\"[cpp]\": {\"editor.wordBasedSuggestions\": <value>}` (`c` 和 `cuda-cpp` 语言也类似)。",
 	"c_cpp.configuration.autocomplete.default.description": "使用活动的 IntelliSense 引擎。",
 	"c_cpp.configuration.autocomplete.disabled.description": "使用 Visual Studio Code 提供的基于字词的补全。",
 	"c_cpp.configuration.errorSquiggles.description": "控制是否将 IntelliSense 引擎检测到的可疑编译错误报告回编辑器。还控制是否报告代码分析警告(如果找不到包含)。标记分析器引擎将忽略此设置。",
@@ -205,6 +205,7 @@
 	"c_cpp.configuration.preferredPathSeparator.markdownDescription": "用作生成的用户路径的路径分隔符的字符。",
 	"c_cpp.configuration.simplifyStructuredComments.markdownDescription": "如果为 `true`，则悬停和自动完成的工具提示将仅显示结构化注释的某些标签。否则，将显示所有注释。",
 	"c_cpp.configuration.doxygen.generateOnType.description": "控制在键入所选注释样式后是否自动插入 Doxygen 注释。",
+	"c_cpp.configuration.doxygen.generateOnCodeAction.description": "控制是否启用生成 Doxygen 注释的代码操作。",
 	"c_cpp.configuration.doxygen.generatedStyle.description": "用作 Doxygen 注释起始行的字符串。",
 	"c_cpp.configuration.doxygen.sectionTags.description": "启用“简化结构化注释”设置后，选择希望在工具提示区域中悬停时显示的 Doxygen 节标记。 ",
 	"c_cpp.configuration.commentContinuationPatterns.items.anyof.string.markdownDescription": "开始多行或单行注释块的模式。多行注释块的延续模式默认为 ` * `，或单行注释块默认为此字符串。",
@@ -326,13 +327,8 @@
 	"c_cpp.debuggers.avoidWindowsConsoleRedirection.description": "如果为 true，则禁用集成终端支持所需的调试对象控制台重定向。",
 	"c_cpp.debuggers.sourceFileMap.markdownDescription": "传递到调试引擎的可选源文件映射。示例: `{ \"<原始源路径>\": \"<当前源路径>\" }`。",
 	"c_cpp.debuggers.processId.anyOf.markdownDescription": "要将调试程序附加到的可选进程 ID。使用 `${command:pickProcess}` 获取要附加到的本地运行进程的列表。请注意，一些平台需要管理员权限才能附加到进程。",
-	"c_cpp.debuggers.program.attach.markdownDescription": {
-		"message": "Full path to the program executable. The debugger will search for a running process matching this executable path and attach to it. If multiple processes match, a selection prompt will be shown. This field is required to load debug symbols for the attached process.",
-		"comment": [
-			"{Locked=\"`program`\"}"
-		]
-	},
-	"c_cpp.debuggers.symbolSearchPath.description": "用于搜索符号(即 pdb)文件的目录列表(以分号分隔)。示例: \"c:\\dir1;c:\\dir2\"。",
+	"c_cpp.debuggers.program.attach.markdownDescription": "程序可执行文件的完整路径。调试器将搜索与此可执行文件路径匹配的正在运行的进程并附加到该进程。如果多个进程匹配，将显示选择提示。加载附加进程的调试符号需要此字段。",
+	"c_cpp.debuggers.symbolSearchPath.description": "用于搜索符号(即 pdb 或 .so)文件的目录的分号分隔列表。示例: \"c:\\dir1;c:\\dir2\"。",
 	"c_cpp.debuggers.dumpPath.description": "指定程序的转储文件的可选完整路径。例如: \"c:\\temp\\app.dmp\"。默认为 null。",
 	"c_cpp.debuggers.enableDebugHeap.description": "如果为 false，将在禁用调试堆的情况下启动该进程。这会将环境变量 \"_NO_DEBUG_HEAP\" 设置为 \"1\"。",
 	"c_cpp.debuggers.symbolLoadInfo.description": "对符号加载的显式控制。",

package/dist/assets/{ms-vscode.cpptools-1.31.0.vsix → ms-vscode.cpptools-1.32.1.vsix}/package.nls.zh-tw.json

@@ -180,7 +180,7 @@
 	"c_cpp.configuration.intelliSenseEngine.default.description": "透過單獨的 IntelliSense 處理序提供內容感知結果。",
 	"c_cpp.configuration.intelliSenseEngine.tagParser.description": "提供不屬於內容意識的 `模糊` 結果。",
 	"c_cpp.configuration.intelliSenseEngine.disabled.description": "關閉 C/C++ 語言服務功能。",
-	"c_cpp.configuration.autocomplete.markdownDescription": "控制自動完成提供者。若設為 `disabled` 且您想要以文字方式完成，您也必須設定 `\"[cpp]\": {\"editor.wordBasedSuggestions\": <value>}` (且 `c` 及 `cuda-cpp` 語言也相同)。",
+	"c_cpp.configuration.autocomplete.markdownDescription": "控制自動完成提供者。若設為 `disabled` 且您想要以文字方式完成，您也必須設定 `\"[cpp]\": {\"editor.wordBasedSuggestions\": <值>}` (且 `c` 及 `cuda-cpp` 語言也相同)。",
 	"c_cpp.configuration.autocomplete.default.description": "使用作用中 IntelliSense 引擎。",
 	"c_cpp.configuration.autocomplete.disabled.description": "使用 Visual Studio Code 所提供的文字型完成。",
 	"c_cpp.configuration.errorSquiggles.description": "該設定會控制是否將 IntelliSense 引擎偵測到的可疑編譯錯誤回報給編輯器。其也會在找不到內容時，控制是否回報程式碼分析警告。標籤剖析器引擎已忽略此設定。",
@@ -205,6 +205,7 @@
 	"c_cpp.configuration.preferredPathSeparator.markdownDescription": "作為所產生使用者路徑之路徑分隔符的字元。",
 	"c_cpp.configuration.simplifyStructuredComments.markdownDescription": "若為 `true`，暫留與自動完成的工具提示只會顯示特定結構化註解標籤，否則將會顯示所有註解。",
 	"c_cpp.configuration.doxygen.generateOnType.description": "控制是否在輸入選擇的註解樣式後自動插入 Doxygen 註解。",
+	"c_cpp.configuration.doxygen.generateOnCodeAction.description": "控制是否啟用產生 Doxygen 註解的程式碼動作。",
 	"c_cpp.configuration.doxygen.generatedStyle.description": "作為 Doxygen 註解起始行的字元字串。",
 	"c_cpp.configuration.doxygen.sectionTags.description": "選取啟用 [簡化結構化註解] 設定時，要在於工具提示區域暫留時顯示的 [Doxygen] 區段標籤。 ",
 	"c_cpp.configuration.commentContinuationPatterns.items.anyof.string.markdownDescription": "開始多行或單行註解區塊的模式。對於多行註解區塊，接續模式預設為 ` * `，或此字串表示單行註解區塊。",
@@ -326,13 +327,8 @@
 	"c_cpp.debuggers.avoidWindowsConsoleRedirection.description": "若為 true，則停用整合式終端機支援需要的偵錯項目主控台重新導向。",
 	"c_cpp.debuggers.sourceFileMap.markdownDescription": "傳遞至偵錯引擎的選擇性來源檔案對應。範例: `{ \"<原始來源路徑>\": \"<目前來源路徑>\" }`。",
 	"c_cpp.debuggers.processId.anyOf.markdownDescription": "要附加偵錯工具的選擇性處理序識別碼。使用 `${command:pickProcess}` 可取得要附加的本機執行中處理序清單。請注意，某些平台需要系統管理員權限才能附加至處理序。",
-	"c_cpp.debuggers.program.attach.markdownDescription": {
-		"message": "Full path to the program executable. The debugger will search for a running process matching this executable path and attach to it. If multiple processes match, a selection prompt will be shown. This field is required to load debug symbols for the attached process.",
-		"comment": [
-			"{Locked=\"`program`\"}"
-		]
-	},
-	"c_cpp.debuggers.symbolSearchPath.description": "要用於搜尋符號 (即 pdb) 檔案的目錄清單 (以分號分隔)。範例: \"c:\\dir1;c:\\dir2\"。",
+	"c_cpp.debuggers.program.attach.markdownDescription": "程式可執行檔的完整路徑。偵錯工具會搜尋符合此可執行路徑的執行中處理序，並連結至該處理序。如果有多個處理序相符，將會顯示選取提示。這是載入已連結處理序之偵錯符號的必要欄位。",
+	"c_cpp.debuggers.symbolSearchPath.description": "要用於搜尋符號 (即 pdb 或 .so) 檔案的目錄清單 (以分號分隔)。範例: \"c:\\dir1;c:\\dir2\"。",
 	"c_cpp.debuggers.dumpPath.description": "指定程式之傾印檔案的選擇性完整路徑。範例: \"c:\\temp\\app.dmp\"。預設為 null。",
 	"c_cpp.debuggers.enableDebugHeap.description": "若為 false，將會啟動已停用偵錯堆積的處理序。這會將環境變數 '_NO_DEBUG_HEAP' 設為 '1'。",
 	"c_cpp.debuggers.symbolLoadInfo.description": "符號載入的明確控制。",

package/dist/assets/{redhat.java-1.54.2026030508.vsix → redhat.java-1.55.2026042408.vsix}/changelog.md

@@ -1,5 +1,23 @@
 # Change Log
 
+## 1.54.0 (April 15th, 2026)
+ * enhancement - Add `serverRunning()` API (v0.14) for progressive loading. See [#4372](https://github.com/redhat-developer/vscode-java/pull/4372).
+ * enhancement - Add JDK 26. See [#4367](https://github.com/redhat-developer/vscode-java/pull/4367).
+ * enhancement - Add inlay hints for format parameters. See [#4350](https://github.com/redhat-developer/vscode-java/issues/4350).
+ * enhancement - Support Scala in Gradle projects. See [#4358](https://github.com/redhat-developer/vscode-java/issues/4358).
+ * enhancement - Progressive project import notifications for tree view. See [JLS#3744](https://github.com/eclipse-jdtls/eclipse.jdt.ls/pull/3744).
+ * enhancement - Add Null Annotation quick-fixes from JDT to jdt.ls. See [JLS#3727](https://github.com/eclipse-jdtls/eclipse.jdt.ls/issues/3727).
+ * enhancement - Remove the first blank line from generated classes created in the default package. See [JLS#3725](https://github.com/eclipse-jdtls/eclipse.jdt.ls/pull/3725).
+ * enhancement - Add quick-assist to convert a class to a record. See [JLS#3723](https://github.com/eclipse-jdtls/eclipse.jdt.ls/pull/3723).
+ * enhancement - Enable change compiler compliance quick-fixes. See [JLS#3743](https://github.com/eclipse-jdtls/eclipse.jdt.ls/pull/3743).
+ * bug fix - Regression in 1.53.0: Gradle import stuck at 70% with Groovy support enabled in custom multi-project settings plugin layout. See [#4360](https://github.com/redhat-developer/vscode-java/issues/4360).
+ * bug fix - Navigating to a Kotlin class now opens the sources instead of the decompiled code. See [#4345](https://github.com/redhat-developer/vscode-java/issues/4345).
+ * bug fix - Quick fix "Add throws declaration" removes backslashes and qute fragments. See [#4314](https://github.com/redhat-developer/vscode-java/issues/4314).
+ * bug fix - Constructor code completion is broken in certain situations. See [#2336](https://github.com/redhat-developer/vscode-java/issues/2336).
+ * dependencies - bump brace-expansion from 1.1.12 to 1.1.13. See [#4373](https://github.com/redhat-developer/vscode-java/pull/4373).
+ * dependencies - bump picomatch. See [#4370](https://github.com/redhat-developer/vscode-java/pull/4370).
+ * dependencies - bump @tootallnate/once and @vscode/test-electron. See [#4355](https://github.com/redhat-developer/vscode-java/pull/4355).
+
 ## 1.53.0 (February 26th, 2026)
  * enhancement - Kotlin imports into Java file are unresolved. See [#531](https://github.com/redhat-developer/vscode-java/issues/531).
  * enhancement - After opening the Kotlin class of a downloaded Maven dependency source, show `.kt` file instead of `.class`. See [#4297](https://github.com/redhat-developer/vscode-java/issues/4297).

package/dist/assets/{redhat.java-1.54.2026030508.vsix → redhat.java-1.55.2026042408.vsix}/package.json

@@ -5,7 +5,7 @@
   "author": "Red Hat",
   "icon": "icons/icon128.png",
   "license": "EPL-2.0",
-  "version": "1.54.2026030508",
+  "version": "1.55.2026042408",
   "publisher": "redhat",
   "bugs": "https://github.com/redhat-developer/vscode-java/issues",
   "preview": false,
@@ -413,6 +413,13 @@
             "scope": "window",
             "order": 80
           },
+          "java.jdt.ls.scalaSupport.enabled": {
+            "type": "boolean",
+            "default": true,
+            "markdownDescription": "[Experimental] Specify whether to enable `scala` plugin in Gradle projects. Defaults to `true`.",
+            "scope": "window",
+            "order": 80
+          },
           "java.jdt.ls.groovySupport.enabled": {
             "type": "boolean",
             "default": true,
@@ -971,7 +978,8 @@
                     "JavaSE-22",
                     "JavaSE-23",
                     "JavaSE-24",
-                    "JavaSE-25"
+                    "JavaSE-25",
+                    "JavaSE-26"
                   ],
                   "description": "Java Execution Environment name. Must be unique."
                 },
@@ -2092,7 +2100,7 @@
     "@types/winston": "^2.4.4",
     "@typescript-eslint/eslint-plugin": "^5.18.0",
     "@typescript-eslint/parser": "^5.18.0",
-    "@vscode/test-electron": "^2.3.8",
+    "@vscode/test-electron": "^2.5.2",
     "css-loader": "^6.7.3",
     "eslint": "^8.13.0",
     "eslint-webpack-plugin": "^3.2.0",
@@ -2101,7 +2109,7 @@
     "minimist": ">=1.2.6",
     "mocha": "^11.1.0",
     "sinon": "^14.0.0",
-    "tar": "^7.5.8",
+    "tar": "^7.5.11",
     "ts-loader": "^9.4.2",
     "typescript": "^4.6.4",
     "webpack": "^5.105.0",

package/dist/assets/{redhat.java-1.54.2026030508.vsix → redhat.java-1.55.2026042408.vsix}/readme.md

@@ -24,7 +24,7 @@ Features
 =========
 ![ screencast ](https://raw.githubusercontent.com/redhat-developer/vscode-java/main/images/vscode-java.0.0.1.gif)
 
-* Supports code from Java 1.8 to Java 25
+* Supports code from Java 1.8 to Java 26
 * Maven pom.xml project support
 * Gradle project support (with experimental Android project import support)
 * Standalone Java files support
@@ -86,6 +86,12 @@ If you need to compile your projects against a different JDK version, it's recom
     "path": "/path/to/jdk-25",
     "default": true
   },
+  ,
+  {
+    "name": "JavaSE-26",
+    "path": "/path/to/jdk-26",
+    "default": true
+  },
 ]
 ```
 The default runtime will be used when you open standalone Java files.
@@ -228,6 +234,7 @@ The following settings are supported:
 * `java.jdt.ls.androidSupport.enabled`: [Experimental] Specify whether to enable Android project importing. When set to `auto`, the Android support will be enabled in Visual Studio Code - Insiders. **Note:** Only works for Android Gradle Plugin `3.2.0` or higher. Defaults to `auto`.
 * `java.jdt.ls.kotlinSupport.enabled`: [Experimental] Specify whether to enable `org.jetbrains.kotlin.jvm` plugin in Gradle projects. Defaults to `true`.
 * `java.jdt.ls.groovySupport.enabled`: [Experimental] Specify whether to enable `groovy` plugin in Gradle projects. Defaults to `true`.
+* `java.jdt.ls.scalaSupport.enabled`: [Experimental] Specify whether to enable `scala` plugin in Gradle projects. Defaults to `true`.
 * `java.completion.postfix.enabled`: Enable/disable postfix completion support. Defaults to `true`.
 * `java.completion.chain.enabled`: Enable/disable chain completion support. Defaults to `false`.
 * `java.completion.matchCase`: Specify whether to match case for code completion. Defaults to `firstLetter`.

package/dist/assets/{scalameta.metals-1.64.0.vsix/readme.md → scalameta.metals-1.65.3.vsix/README.md}

@@ -48,7 +48,7 @@ by clicking on this badge
 [![Install Metals extension](https://img.shields.io/badge/metals-vscode-blue.png)](https://github.com/scalameta/metals-vscode/blob/HEAD/vscode:extension/scalameta.metals)
 or via the VS Code editor:
 
-![install stable version](https://github.com/scalameta/gh-pages-images/blob/master/metals/vscode/Qew0fNH.png?raw=true)
+![install stable version](https://raw.githubusercontent.com/scalameta/gh-pages-images/main/metals/vscode/Qew0fNH.png)
 
 Next, open a directory containing your Scala code. The extension activates when
 the main directory contains `build.sbt` or `build.sc` file, a Scala file is
@@ -62,14 +62,14 @@ with [SNAPSHOT](#SNAPSHOT) releases of Metals server. Using pre-release versions
 may result in less stable experience and it is not intented for beginners.
 Pre-release versions follow `major.minor.PATCH` versioning.
 
-![Install the pre-release extension](https://github.com/scalameta/gh-pages-images/blob/master/metals/vscode/CzOTleE.png?raw=true)
+![Install the pre-release extension](https://raw.githubusercontent.com/scalameta/gh-pages-images/main/metals/vscode/CzOTleE.png)
 
 ## Importing a build
 
 The first time you open Metals in a new workspace it prompts you to import the build.
 Click "Import build" to start the installation step.
 
-![Import build](https://github.com/scalameta/gh-pages-images/blob/master/metals/Image/0VqZWay.png?raw=true)
+![Import build](https://raw.githubusercontent.com/scalameta/gh-pages-images/main/metals/Image/0VqZWay.png)
 
 - "Not now" disables this prompt for 2 minutes.
 - "Don't show again" disables this prompt forever, use `rm -rf .metals/` to re-enable
@@ -93,7 +93,7 @@ Update the "Sbt Script" setting to use a custom `sbt` script instead of the
 default Metals launcher if you need further customizations like reading environment
 variables.
 
-![Sbt Launcher](https://github.com/scalameta/gh-pages-images/blob/master/metals/vscode/NuwEBe4.png?raw=true)
+![Sbt Launcher](https://raw.githubusercontent.com/scalameta/gh-pages-images/main/metals/vscode/NuwEBe4.png)
 
 ### Speeding up import
 
@@ -111,21 +111,21 @@ to learn how to speed up build import.
 When you change `build.sbt` or sources under `project/`, you will be prompted to
 re-import the build.
 
-![Import sbt changes](https://github.com/scalameta/gh-pages-images/blob/master/metals/Image/72kdZkL.png?raw=true)
+![Import sbt changes](https://raw.githubusercontent.com/scalameta/gh-pages-images/main/metals/Image/72kdZkL.png)
 
 ### Manually trigger build import
 
 To manually trigger a build import, execute the "Import build" command through
 the command palette (`Cmd + Shift + P`).
 
-![Import build command](https://github.com/scalameta/gh-pages-images/blob/master/metals/Image/QHLKt8u.png?raw=true)
+![Import build command](https://raw.githubusercontent.com/scalameta/gh-pages-images/main/metals/Image/QHLKt8u.png)
 
 ## Run doctor
 
 Execute the "Run Doctor" through the command palette to troubleshoot potential
 configuration problems in your workspace.
 
-![Run doctor command](https://github.com/scalameta/gh-pages-images/blob/master/metals/Image/K02g0UM.png?raw=true)
+![Run doctor command](https://raw.githubusercontent.com/scalameta/gh-pages-images/main/metals/Image/K02g0UM.png)
 
 ## Configure Java version
 
@@ -141,7 +141,7 @@ environment variable (via
 If no matching Java found, a JDK will be downloaded using
 [coursier](https://get-coursier.io).
 
-#### Settings
+#### Settings:
 
 - `Java Version` - minimum JDK version accepted for running Metals server. If
   none found, this is also the version that will be downloaded using coursier.
@@ -155,12 +155,12 @@ for running the build server but appropriate `-release` flags are added for
 compilation. By default Metals uses JDK defined by `JAVA_HOME` environment
 variable, if the variable is not set is falls to using the Metals's JDK.
 
-#### Settings
+#### Settings:
 
 - `Java Home` - path to project's JDK's Home. Note: this setting isn't respected
   for `Bazel`.
 
-![Java Home setting](https://github.com/scalameta/gh-pages-images/blob/master/metals/vscode/sKrPKk2.png?raw=true)
+![Java Home setting](https://raw.githubusercontent.com/scalameta/gh-pages-images/main/metals/vscode/sKrPKk2.png)
 
 Note: Project's JDK version should be greater or equal to Metals's server JDK
 version for features like completions to work correctly.
@@ -184,7 +184,7 @@ Use the 'Custom Repositories' setting for the Metals VS Code extension to tell
 artifacts from your private artifact repository.
 
 Use `.jvmopts` to set sbt options
-(<https://www.scala-sbt.org/1.0/docs/Proxy-Repositories.html>) for
+(https://www.scala-sbt.org/1.0/docs/Proxy-Repositories.html) for
 `sbt bloopInstall` which resolves library dependencies. You can also provide a
 custom sbt script (see 'Custom sbt launcher').
 
@@ -248,15 +248,15 @@ for more context.
 Run the "Explorer: Focus on Outline View" command to open the symbol outline for
 the current file in the sidebar.
 
-![Document Symbols Outline](https://github.com/scalameta/gh-pages-images/blob/master/metals/vscode/T0kVJsr.gif?raw=true)
+![Document Symbols Outline](https://raw.githubusercontent.com/scalameta/gh-pages-images/main/metals/vscode/T0kVJsr.gif)
 
 Run the "Open Symbol in File" command to search for a symbol in the current file
 without opening the sidebar.
 
-![Document Symbols Command](https://github.com/scalameta/gh-pages-images/blob/master/metals/vscode/0PJ4brd.png?raw=true)
+![Document Symbols Command](https://raw.githubusercontent.com/scalameta/gh-pages-images/main/metals/vscode/0PJ4brd.png)
 
 As you type, the symbol outline is also visible at the top of the file.
-![Document Symbols Outline](https://github.com/scalameta/gh-pages-images/blob/master/metals/vscode/L217n4q.png?raw=true)
+![Document Symbols Outline](https://raw.githubusercontent.com/scalameta/gh-pages-images/main/metals/vscode/L217n4q.png)
 
 ## Go to parent code lenses
 
@@ -273,7 +273,7 @@ using two commands:
 - `Metals: Go to super method` - immediately goes to the parent of the method the cursor is pointing to
 
 - `Metals: Reveal super method hierachy` - displays the full method hierachy and enables to move to any parent,
-it is best used with the Metals Quick Pick extension.
+  it is best used with the Metals Quick Pick extension.
 
 You can also bind those commands to a shortcut.
 
@@ -285,9 +285,9 @@ There is a great number of templates already available and it should be easy to
 To start the setup you can use the Metals: New Scala project command, which works as following:
 
 1. Choose the template and then:
-    1. Use the proposed templates.
-    2. Choose "Discover more" and then choose from the list downloaded from the Giter8 wiki page.
-    3. Input a custom Github repository following the `organization/repo` schema.
+   1. Use the proposed templates.
+   2. Choose "Discover more" and then choose from the list downloaded from the Giter8 wiki page.
+   3. Input a custom Github repository following the `organization/repo` schema.
 2. Navigate to the parent directory that you want to create your new project in.
 3. Choose the name or accept the default one.
 
@@ -325,7 +325,7 @@ project's modules. From this panel it's possible to
 - run/debug test
 - navigate to test's definition.
 
-![test-explorer](https://github.com/scalameta/gh-pages-images/blob/master/metals/vscode/Z3VtS0O.gif?raw=true)
+![test-explorer](https://raw.githubusercontent.com/scalameta/gh-pages-images/main/metals/vscode/Z3VtS0O.gif)
 
 NOTE: While Metals detects test suites for most of existing testing
 frameworks, support for recognizing individual tests is more limited.
@@ -340,11 +340,11 @@ individual test discovery:
 If you encounter an error, create an
 [issue](https://github.com/scalameta/metals/issues).
 
-![test-explorer](https://github.com/scalameta/gh-pages-images/blob/master/metals/vscode/Z3VtS0O.gif?raw=true)
+![test-explorer](https://raw.githubusercontent.com/scalameta/gh-pages-images/main/metals/vscode/Z3VtS0O.gif)
 
 ### via code lenses
 
-![lenses](https://github.com/scalameta/gh-pages-images/blob/master/metals/vscode/5nTnrcS.png?raw=true)
+![lenses](https://raw.githubusercontent.com/scalameta/gh-pages-images/main/metals/vscode/5nTnrcS.png)
 
 For each main or test class Metals shows two code lenses `run | debug` or
 `test | test debug`, which show up above the definition as a kind of virtual
@@ -476,26 +476,26 @@ nativeConfig ~= { c =>
 
 ## On type formatting for multiline string formatting
 
-![on-type](https://github.com/scalameta/gh-pages-images/blob/master/metals/vscode/a0O2vCs.gif?raw=true)
+![on-type](https://raw.githubusercontent.com/scalameta/gh-pages-images/main/metals/vscode/a0O2vCs.gif)
 
 To properly support adding `|` in multiline strings we are using the
 `onTypeFormatting` method. The functionality is enabled by default, but you can
 disable/enable `onTypeFormatting` inside Visual Studio Code settings by checking
 `Editor: Format On Type`:
 
-![on-type-setting](https://github.com/scalameta/gh-pages-images/blob/master/metals/vscode/s6nT9rC.png?raw=true)
+![on-type-setting](https://raw.githubusercontent.com/scalameta/gh-pages-images/main/metals/vscode/s6nT9rC.png)
 
 ## Formatting on paste for multiline strings
 
 Whenever text is paste into a multiline string with `|` it will be properly
 formatted by Metals:
 
-![format-on-paste](https://github.com/scalameta/gh-pages-images/blob/master/metals/vscode/fF0XWYC.gif?raw=true)
+![format-on-paste](https://raw.githubusercontent.com/scalameta/gh-pages-images/main/metals/vscode/fF0XWYC.gif)
 
 This feature is enabled by default. If you need to disable/enable formatting on
 paste in Visual Studio Code you can check the `Editor: Format On Paste` setting:
 
-![format-on-paste-setting](https://github.com/scalameta/gh-pages-images/blob/master/metals/vscode/rMrk27F.png?raw=true)
+![format-on-paste-setting](https://raw.githubusercontent.com/scalameta/gh-pages-images/main/metals/vscode/rMrk27F.png)
 
 ## Worksheets
 
@@ -507,7 +507,7 @@ the scenes worksheets are powered by the great work done in
 ### Getting started with Worksheets
 
 To get started with a worksheet you can either use the `metals.new-scala-file`
-command and select *Worksheet* or create a file called `*.worksheet.sc`.
+command and select _Worksheet_ or create a file called `*.worksheet.sc`.
 This format is important since this is what tells Metals that it's meant to be
 treated as a worksheet and not just a Scala script. Where you create the
 script also matters. If you'd like to use classes and values from your
@@ -631,4 +631,4 @@ extension to use default IntelliJ shortcuts with VS Code.
 ## GitHub Codespaces and GitHub.dev support
 
 See
-<https://scalameta.org/metals/docs/editors/online-ides#github-codespaces-and-githubdev>
+https://scalameta.org/metals/docs/editors/online-ides#github-codespaces-and-githubdev

package/dist/assets/{scalameta.metals-1.64.0.vsix → scalameta.metals-1.65.3.vsix}/jvm-bytecode.json

@@ -20,7 +20,7 @@
       "include": "#values"
     },
     {
-      "include": "#constructors"
+      "include": "#constructor"
     },
     {
       "include": "#methods"