JSDocs в VSCode

Меня зовут Алекс Гусев. В этой публикации я очень кратко раскрываю, почему переход с IntelliJ IDEA (PhpStorm) на VSCode ломает привычную работу с JSDoc в JavaScript-проектах.

https://habr.com/ru/articles/980286/

#javascript #jsdoc #vscode #lsp #анализ_кода

We know that there are some #emacs fans among our followers. We would like to see a blog article about using JabRef's #LSP server with Emacs as a client. The LSP server covers the integrity check and consistency check of #JabRef.
Not only that, but we are happy for a quick write-up from a real human, not some AI slop. The blog post will, of course, feature your name.

https://github.com/JabRef/jabref/issues/14656

#java #javafx #academia #bibtex #opensource

[Перевод] Поддержка LSP в Claude Code: возможности, настройка и текущие проблемы

Команда AI for Devs подготовила перевод статьи о поддержке LSP в Claude Code. Начиная с версии 2.0.74 агент получил доступ к семантике кода: переходы к определениям, поиск ссылок и иерархия вызовов. Это заметно ускоряет работу с большими кодовыми базами, но на практике функциональность пока сыровата и требует обходных решений. Разбираемся, как включить LSP, какие языки поддерживаются и с какими ограничениями придётся столкнуться.

https://habr.com/ru/articles/979506/

#Claude_Code #LSP #инструменты_разработчика #навигация_по_коду #ИИ_для_программирования #плагины #кодинг

Polymorphism không phải để tái sử dụng code, mà là về sự tin cậy và khả năng thay thế (substitutability) an toàn. Một thiết kế tốt đảm bảo bạn có thể thay thế các thành phần mà không làm hỏng hệ thống hay thay đổi hành vi mong đợi. Liskov Substitution Principle (LSP) là ranh giới giữa an toàn và rủi ro. Hãy hỏi: "Liệu có thể thay thế thứ này mà không phá vỡ ý nghĩa?" thay vì chỉ hỏi làm sao để tái sử dụng code.

#Polymorphism #LSP #CSharp #SystemDesign #SoftwareArchitecture #KiếnTrúcPhầnMềm #Lập

Claude Code gets native LSP support

https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md

#HackerNews #ClaudeCode #LSP #nativeSupport #coding #news #techupdates

Let's say you want to do good type-checking for the #Python project you're working on. You pick a tool, maybe you use it as an #LSP also (so your editor can show you errors, too). As an example, I'm using #Ty at the moment. There's three places this might be installed: globally (e.g., `brew install ty`), as a dev-only dependency inside your project (e.g., `uv add --dev ty`), or -- and this one might surprise you -- it might only be used and installed by `pre-commit`, which builds a separate environment for each needed tool (which is great for instance where I use `codespell` as a `pre-commit` check, which seems to need some higher version of Python than my actual project).

Where should you install it?

If you're the only one on your team running it, globally is fine. If more than just you, then absolutely as a dev-only dependency inside your project ... and **maybe** globally as well.

The only real problem is updates. If you use a reasonable global install scheme, updates will be easy. They're less easy inside your project or in `pre-commit`. And you might care one way or the other! I **don't** want updates! I **do** want updates!

As for Python type-checking, `ty` seems good so far, but not enough experience with it yet. `basedpyright`, `pyrefly`, and `ruff` all good. These four are my favorites.

#BasedPyright #Pyrefly #Ruff #PreCommit #CodeSpell #Homebrew

Delighted to find that Emacs' `lsp-mode` package already has support for the Python type-checker `ty` (it was merged back in May https://github.com/emacs-lsp/lsp-mode/pull/4785). If you've got it installed in your virtual environment then it may well "Just Work(tm)" out of the box when you next open a file in your project (it did for me).

Emacs and its users, package developers, contributors never ceases to amaze and please me.

#emacs #lsp #lspmode