refactor!: Переименование поля ИндексИтерации в НомерИтерации

[Stivo182]

Summary by CodeRabbit

• Style
  • Updated naming of the iteration index to iteration number in user-facing tables, output, and documentation for improved clarity and consistency. No changes to functionality or behavior.

[coderabbitai]

Walkthrough

The changes consist of renaming the identifier for the iteration index from "ИндексИтерации" to "НомерИтерации" across code and comments in the benchmark runner and benchmarking module. This includes updates to function parameters, structure fields, table columns, and related documentation. No logic or control flow is affected.

Changes

File(s)	Change Summary
src/BenchmarkOneScript/core/Классы/ЗапускательБенчмарков.os	Renamed all instances of "ИндексИтерации" to "НомерИтерации" in parameters, fields, comments, and output formatting. Updated function signature for ВыполнитьИтерацию.
src/BenchmarkOneScript/core/Модули/Бенчмаркинг.os	Updated documentation comment: renamed structure field from "ИндексИтерации" to "НомерИтерации".

Poem

In code where benchmarks swiftly run,
An index’s name is now redone.
"ИндексИтерации" bows away,
"НомерИтерации" here to stay!
With tidy names, our scripts advance—
The rabbits hop, the numbers dance!
🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5661630 and b904244.

📒 Files selected for processing (2)

• src/BenchmarkOneScript/core/Классы/ЗапускательБенчмарков.os (7 hunks)
• src/BenchmarkOneScript/core/Модули/Бенчмаркинг.os (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (12)

• GitHub Check: sonar / test
• GitHub Check: build (windows-latest, stable)
• GitHub Check: build (ubuntu-latest, stable)
• GitHub Check: build (ubuntu-latest, dev)
• GitHub Check: build (windows-latest, dev)
• GitHub Check: build (macos-latest, stable)
• GitHub Check: sonar / test
• GitHub Check: build (windows-latest, dev)
• GitHub Check: build (macos-latest, stable)
• GitHub Check: build (macos-latest, dev)
• GitHub Check: build (windows-latest, stable)
• GitHub Check: build (ubuntu-latest, stable)

🔇 Additional comments (9)

src/BenchmarkOneScript/core/Модули/Бенчмаркинг.os (1)

24-24: Consistent documentation update
The field name in the result-structure comment is updated from "ИндексИтерации" to "НомерИтерации", matching the refactored code.

src/BenchmarkOneScript/core/Классы/ЗапускательБенчмарков.os (8)

47-47: Rename comment field to НомерИтерации
The inline documentation for the measurements table now correctly lists 'НомерИтерации' instead of the old identifier.

---

315-315: Rename function parameter to НомерИтерации
The signature of ВыполнитьИтерацию has been updated to use the new parameter name, ensuring consistency with field renaming.

---

328-328: Initialize the renamed result field
The assignment РезультатИтерации.НомерИтерации = НомерИтерации correctly mirrors the updated field and parameter.

---

335-335: Conditional check on НомерИтерации
The first-iteration check now references the renamed variable, preserving existing behavior.

---

536-536: Format output with НомерИтерации
The formatted log line now includes the new iteration number field in the output template.

---

665-665: Include НомерИтерации in result structure initialization
The default result struct now initializes the renamed field to 0, aligning with other structure defaults.

---

681-681: Update table-schema comment for НомерИтерации
The comment documenting the measurement-table schema correctly lists 'НомерИтерации'.

---

691-691: Add НомерИтерации column to measurement table
The table column definition now includes 'НомерИтерации', ensuring the data model matches the refactored field.

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[sonar-openbsl-ru-qa-bot]

Quality Gate failed

• 1 New Issues (is greater than 0)

Project ID: benchmark

View in SonarQube