feat(types): ссылка «См.» на форму по полному имени

[nixel2007]

Пункт 3.29 рекомендации «Типизация кода»: «Ссылка на форму указывается по полному имени формы».

// Параметры:
//  Форма - См. Справочник.Товары.Форма.ФормаЭлемента
Процедура ПриСозданииНаСервере(Форма)
	Ссылка = Форма.Объект.Ссылка;
	Форма.Элементы.Артикул.Видимость = Истина;

Что было

Тип не выводился вовсе. Синтетический тип формы регистрируется под именем «базовый тип формы + ссылка на объект метаданных» — ФормаКлиентскогоПриложения.Справочник.Товары.Форма.ФормаЭлемента (FormTypesProvider#selfTypeQualifiedName), а в ссылке пишут только вторую половину. Разбор ссылки пробовал табличную часть, реквизит объекта и полное имя типа — ни одно не подошло.

Что сделано

Разбор См.-ссылки, не найдя пути в метаданных, спрашивает FormByNameResolver — тот самый, что типизирует ПолучитьФорму("<полное имя>"): он перебирает приставки базовых типов форм и, если не нашёл точного имени, пробует основную форму объекта. Новой логики поиска не появилось, добавилась связка.

Проверки

SeeFormRefInferenceTest: ссылка даёт тип конкретной формы, а через него — основной реквизит (Форма.Объект.Ссылка → СправочникСсылка.Справочник1) и элемент формы (Форма.Элементы.Наименование → ПолеФормы). Оба теста красные до правки.

Прогоны *types.* и *providers.* — зелёные.

Summary by CodeRabbit

• Bug Fixes

  • Improved type and hyperlink resolution for qualified form references.
  • Form references in documentation now correctly resolve to the associated form type, attributes, and elements.

• Tests

  • Added coverage for form reference type inference and updated hyperlink resolution test setup.

[coderabbitai]

Warning

Review limit reached

@nixel2007, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 8 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: e907d7b4-d8f8-437e-807b-b83381a9f2f9

📥 Commits

Reviewing files that changed from the base of the PR and between c943eba and f58275a.

📒 Files selected for processing (1)

• src/main/java/com/github/_1c_syntax/bsl/languageserver/types/index/SymbolTypeIndex.java

📝 Walkthrough

Walkthrough

SymbolTypeIndex now resolves qualified form references through FormByNameResolver when existing resolution paths fail. Tests verify inferred form types, object reference attributes, and form elements.

Changes

Form reference resolution

Layer / File(s)	Summary
Form resolver fallback src/main/java/com/github/_1c_syntax/bsl/languageserver/types/index/SymbolTypeIndex.java	SymbolTypeIndex stores FormByNameResolver and uses it as a fallback in resolveSeeReference. Resolved forms are returned as a single-element TypeSet.
Form inference validation src/test/java/com/github/_1c_syntax/bsl/languageserver/types/SeeFormRefInferenceTest.java, src/test/java/com/github/_1c_syntax/bsl/languageserver/types/index/SymbolTypeIndexHyperlinkTest.java	Tests verify inferred form types and update test construction with the resolver dependency.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

• 1c-syntax/bsl-language-server#4337: Modifies related SymbolTypeIndex and FormByNameResolver form-name resolution.
• 1c-syntax/bsl-language-server#4183: Centralizes related См. reference resolution logic in SymbolTypeIndex.
• 1c-syntax/bsl-language-server#4374: Adds related fallback resolution for qualified См. references.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes support for resolving «См.» references to forms by their full names.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/types-see-ref-form

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In
`@src/main/java/com/github/_1c_syntax/bsl/languageserver/types/index/SymbolTypeIndex.java`:
- Around line 386-392: Update the JavaDoc for resolveSeeReference to document
form-name resolution as a fallback, then update the corresponding user-facing
documentation in both docs/ and docs/en/. Describe the supported behavior and
usage without exposing resolver implementation details; leave the existing
formByNameResolver implementation unchanged.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 5d350d4f-7424-45bd-b445-481a7e23d4b0

📥 Commits

Reviewing files that changed from the base of the PR and between 3449901 and c8d5132.

📒 Files selected for processing (3)

• src/main/java/com/github/_1c_syntax/bsl/languageserver/types/index/SymbolTypeIndex.java
• src/test/java/com/github/_1c_syntax/bsl/languageserver/types/SeeFormRefInferenceTest.java
• src/test/java/com/github/_1c_syntax/bsl/languageserver/types/index/SymbolTypeIndexHyperlinkTest.java

[github-actions]

Test Results

 3 990 files  + 6   3 990 suites  +6   52m 33s ⏱️ - 1m 37s
 4 132 tests + 2   4 061 ✅ + 2   71 💤 ±0  0 ❌ ±0 
24 792 runs  +12  24 362 ✅ +12  430 💤 ±0  0 ❌ ±0 

Results for commit f58275a. ± Comparison against base commit 3449901.

♻️ This comment has been updated with latest results.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud