Skip to content

Conversation

@theshadowco
Copy link
Member

@theshadowco theshadowco commented Jan 2, 2026

Описание

Связанные задачи

Closes #561

Чеклист

Общие

  • Ветка PR обновлена из develop
  • Отладочные, закомментированные и прочие, не имеющие смысла участки кода удалены
  • Изменения покрыты тестами
  • Обязательные действия перед коммитом выполнены (запускал команду gradlew precommit)

Дополнительно

Summary by CodeRabbit

  • Chores
    • Updated internal dependencies to the latest patch versions to improve stability and ensure compatibility across the application.

✏️ Tip: You can customize this high-level summary in your review settings.

@coderabbitai
Copy link

coderabbitai bot commented Jan 2, 2026

📝 Walkthrough

Walkthrough

Updated bsl-common-library dependency from version 0.9.0 to 0.9.1 in the Gradle Kotlin DSL configuration file. This is a patch-level version bump with no other code modifications.

Changes

Cohort / File(s) Summary
Dependency Version Update
build.gradle.kts
Bumped bsl-common-library from 0.9.0 to 0.9.1

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 A tiny bump, from point-oh-nine,
To zero-point-one, a patch divine!
The catalog parsing now runs clean,
No more unknown types in between,
A rabbit's hop toward parsing zen! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning, 1 inconclusive)
Check name Status Explanation Resolution
Linked Issues check ⚠️ Warning The PR claims to fix issue #561 (unknown valueType bug) but only updates bsl-common-library from 0.9.0 to 0.9.1; there is no evidence this dependency update resolves the valueType parsing error. Verify that the bsl-common-library 0.9.1 update actually fixes the valueType issue, and provide explanation in the PR description or update the approach if the fix requires additional code changes.
Title check ❓ Inconclusive The title is in Russian and references issue #561, but the actual code change only updates a dependency version, which does not clearly address the unknown valueType bug described in the issue. Clarify whether the dependency update fixes the valueType issue, or provide a more descriptive title in English explaining what the change accomplishes.
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Out of Scope Changes check ✅ Passed The pull request only contains a dependency version update, which is directly related to addressing the linked issue regarding the valueType bug.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
  • 📝 Generate docstrings

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

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e77a8b9 and 1d7ff57.

📒 Files selected for processing (1)
  • build.gradle.kts
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (12)
  • GitHub Check: build (21, macOS-latest)
  • GitHub Check: build (21, windows-latest)
  • GitHub Check: QA
  • GitHub Check: build (17, windows-latest)
  • GitHub Check: build (17, macOS-latest)
  • GitHub Check: build (25, macOS-latest)
  • GitHub Check: build (21, ubuntu-latest)
  • GitHub Check: build (25, windows-latest)
  • GitHub Check: build (21, macOS-latest)
  • GitHub Check: build (21, windows-latest)
  • GitHub Check: build (17, ubuntu-latest)
  • GitHub Check: build (25, ubuntu-latest)

// прочее
implementation("commons-io", "commons-io", "2.18.0")
implementation("io.github.1c-syntax", "bsl-common-library", "0.9.0")
implementation("io.github.1c-syntax", "bsl-common-library", "0.9.1")
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Check Maven Central for version 0.9.1 availability
echo "=== Checking Maven Central for bsl-common-library 0.9.1 ==="
curl -s -I "https://repo1.maven.org/maven2/io/github/1c-syntax/bsl-common-library/0.9.1/bsl-common-library-0.9.1.jar" | head -1

# Check available versions
echo -e "\n=== Checking available versions around 0.9.1 ==="
curl -s "https://repo1.maven.org/maven2/io/github/1c-syntax/bsl-common-library/" | grep -o '0\.9\.[0-9]*' | sort -u

Repository: 1c-syntax/mdclasses

Length of output: 197


🌐 Web query:

bsl-common-library 0.9.1 release notes 1c-syntax GitHub

💡 Result:

I couldn't find a GitHub release or release notes for bsl-common-library version 0.9.1. The latest published version I can find is 0.9.0 (project homepage and docs show 0.9.0). [1][2][3]

Sources:

  • Maven / mvnrepository entry for bsl-common-library (shows 0.9.0). [1]
  • 1c-syntax GitHub organization page. [2]
  • Javadoc / package page for bsl-common-library (current version 0.9.0). [3]

If you want, I can check the repository's Releases page or tags on GitHub now and report back.


🏁 Script executed:

#!/bin/bash
# Search for references to issue #561 and catalog parsing tests
echo "=== Searching for issue #561 references ==="
rg -i "561|апк.*ферм|cataloglist" --type md --type kt --type java --type gradle

echo -e "\n=== Checking for parsing/catalog related tests ==="
fd -e kt -e java | xargs rg -l "catalog|parse|valueType" -i | head -10

Repository: 1c-syntax/mdclasses

Length of output: 878


🏁 Script executed:

#!/bin/bash
# Check GitHub releases for bsl-common-library more directly
echo "=== Checking GitHub API for bsl-common-library releases ==="
curl -s "https://api.github.com/repos/1c-syntax/bsl-common-library/releases" | grep -E '"tag_name"|"name"|"published_at"' | head -20

echo -e "\n=== Checking recent tags ==="
curl -s "https://api.github.com/repos/1c-syntax/bsl-common-library/tags" | grep -E '"name"' | head -10

echo -e "\n=== Checking current mdclasses repository for issue #561 ==="
rg "561" --type md

echo -e "\n=== Looking at CatalogTest for parsing/valueType tests ==="
head -50 src/test/java/com/github/_1c_syntax/bsl/mdo/CatalogTest.java

Repository: 1c-syntax/mdclasses

Length of output: 3071


🌐 Web query:

bsl-common-library GitHub releases 0.9.1

💡 Result:

I couldn't find a GitHub release v0.9.1 for bsl-common-library. The latest published version appears to be 0.9.0 (see Javadoc and Maven listings), and the project repository is 1c-syntax/bsl-common-library on GitHub. [1][2][3]

Sources:

  • bsl-common-library Javadoc (current version 0.9.0). [1]
  • Maven / mvnrepository listing for bsl-common-library (0.9.0). [2]
  • 1c-syntax GitHub organization (repository: bsl-common-library). [3]

🏁 Script executed:

#!/bin/bash
# Get the full release information for v0.9.1
echo "=== Full v0.9.1 release details from bsl-common-library ==="
curl -s "https://api.github.com/repos/1c-syntax/bsl-common-library/releases/tags/v0.9.1" | jq '.body // .name'

echo -e "\n=== Check if issue #561 is in bsl-common-library ==="
curl -s "https://api.github.com/repos/1c-syntax/bsl-common-library/issues/561" | jq '.title, .state, .body' 2>/dev/null | head -20

echo -e "\n=== Check for recent commits in v0.9.1 ==="
curl -s "https://api.github.com/repos/1c-syntax/bsl-common-library/compare/v0.9.0...v0.9.1" | jq '.commits[].message' | head -10

Repository: 1c-syntax/mdclasses

Length of output: 549


🏁 Script executed:

#!/bin/bash
# Look for issue reference in build.gradle.kts or git commits
echo "=== Searching for issue references in the PR/commits ==="
rg "561|issue|bug|fix" build.gradle.kts

echo -e "\n=== Check git log for recent commits mentioning the dependency ==="
git log --oneline --all -20 | rg -i "deps|bsl|common|library"

echo -e "\n=== Look at build.gradle.kts context around line 62 ==="
sed -n '55,70p' build.gradle.kts

Repository: 1c-syntax/mdclasses

Length of output: 961


Add regression test and improve commit message.

Version 0.9.1 of bsl-common-library is published and includes the relevant fix: "Added types for Electronic Catalog List and Document List" which addresses the valueType parsing issue. However:

  1. Add a regression test in this repository to verify that the previously failing case (cfg:CatalogList.АпкФермы with unknown valueType) now parses correctly
  2. Improve the commit message from "new deps" to something more descriptive like "Bump bsl-common-library to 0.9.1 for catalog valueType parsing fix"
  3. Complete the PR checklist items (tests and precommit checks)
🤖 Prompt for AI Agents
In build.gradle.kts at line 62, after bumping bsl-common-library to 0.9.1, add a
regression test that loads/parses the previously failing resource
(cfg:CatalogList.АпкФермы) and asserts the valueType is now recognized (or
parsing succeeds without error), update the commit message from "new deps" to
"Bump bsl-common-library to 0.9.1 for catalog valueType parsing fix", and ensure
you complete the PR checklist by adding the new test to the test suite and
re-running precommit checks/CI (fix any lint/test failures) before pushing.

@sonarqubecloud
Copy link

sonarqubecloud bot commented Jan 2, 2026

@github-actions
Copy link
Contributor

github-actions bot commented Jan 2, 2026

Test Results

  603 files  ±0    603 suites  ±0   9m 34s ⏱️ +33s
  284 tests ±0    284 ✅ ±0  0 💤 ±0  0 ❌ ±0 
2 646 runs  ±0  2 646 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 1d7ff57. ± Comparison against base commit e77a8b9.

♻️ This comment has been updated with latest results.

@theshadowco theshadowco merged commit b61b56f into develop Jan 2, 2026
25 checks passed
@theshadowco theshadowco deleted the feature/fixUnknownValueType branch January 2, 2026 08:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] Unknown valueType [cfg:CatalogList.АпкФермы]

2 participants