Skip to content

Fix reflection-docblock deprecation warnings #64

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

BrianHenryIE
Copy link

@BrianHenryIE BrianHenryIE commented Jun 12, 2025

Fix deprecation warnings in phpdocumentor/reflection-docblock

phpDocumentor/ReflectionDocBlock#361

Proposed Changes

Summary by CodeRabbit

  • Refactor
    • Improved the underlying PHPDoc parsing mechanism for better consistency across components without changing any user-facing features or behaviors.

Copy link

coderabbitai bot commented Jun 12, 2025

Walkthrough

The changes update the instantiation of the PHPDoc parser throughout several model classes. The code now uses DocFactoryProvider::getDocFactory()->create(...) instead of the previous Utils::createDocBlockInstance()->create(...) method. All logic for parsing doc comments and extracting tags remains unchanged, with no modifications to public interfaces.

Changes

File(s) Change Summary
src/voku/SimplePhpParser/Model/PHPClass.php
src/voku/SimplePhpParser/Model/PHPTrait.php
Replaced PHPDoc parser instantiation with DocFactoryProvider::getDocFactory()->create(...) in property doc parsing.
src/voku/SimplePhpParser/Model/PHPFunction.php Updated doc comment parsing methods to use DocFactoryProvider::getDocFactory()->create(...).
src/voku/SimplePhpParser/Model/PHPMethod.php Changed DocBlock creation to use DocFactoryProvider::getDocFactory()->create(...) in method doc parsing.
src/voku/SimplePhpParser/Model/PHPParameter.php Removed extraneous blank line after PHPDoc parser instantiation; parser instantiation unchanged.
src/voku/SimplePhpParser/Model/PHPProperty.php Modified property doc parsing to use DocFactoryProvider::getDocFactory()->create(...).

Poem

In burrows deep, with code anew,
The rabbits swapped a parsing crew.
No more the Utils, now Factory reigns,
Creating DocBlocks with fewer chains.
The docs are parsed, the tags are clear,
Hippity-hop, the code’s in gear!
🐇✨


📜 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 8ce16ff and 93c7fd3.

📒 Files selected for processing (6)
  • src/voku/SimplePhpParser/Model/PHPClass.php (2 hunks)
  • src/voku/SimplePhpParser/Model/PHPFunction.php (2 hunks)
  • src/voku/SimplePhpParser/Model/PHPMethod.php (1 hunks)
  • src/voku/SimplePhpParser/Model/PHPParameter.php (0 hunks)
  • src/voku/SimplePhpParser/Model/PHPProperty.php (2 hunks)
  • src/voku/SimplePhpParser/Model/PHPTrait.php (2 hunks)
💤 Files with no reviewable changes (1)
  • src/voku/SimplePhpParser/Model/PHPParameter.php
🚧 Files skipped from review as they are similar to previous changes (5)
  • src/voku/SimplePhpParser/Model/PHPProperty.php
  • src/voku/SimplePhpParser/Model/PHPClass.php
  • src/voku/SimplePhpParser/Model/PHPFunction.php
  • src/voku/SimplePhpParser/Model/PHPMethod.php
  • src/voku/SimplePhpParser/Model/PHPTrait.php
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Codacy Static Code Analysis
✨ Finishing Touches
  • 📝 Generate Docstrings

🪧 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.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Summary of Changes

Hello @BrianHenryIE, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request aims to resolve deprecation warnings related to the phpdocumentor/reflection-docblock dependency. It updates the code to use the current recommended way of instantiating the DocBlock factory, ensuring compatibility and removing warnings.

Highlights

  • Dependency Usage Update: Updated the usage of phpdocumentor/reflection-docblock to use the recommended DocBlockFactory::createInstance() method instead of the deprecated Utils::createDocBlockInstance().
  • Deprecation Warning Fix: Addressed deprecation warnings originating from the phpdocumentor/reflection-docblock library by switching to the non-deprecated factory method.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configureGemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request addresses deprecation warnings by updating how phpDocumentor\Reflection\DocBlockFactory instances are created. It is suggested to use the existing voku\SimplePhpParser\Parsers\Helper\DocFactoryProvider::getDocFactory() instead of DocBlockFactory::createInstance() directly to leverage the cached factory instance for better performance.

@@ -385,7 +386,7 @@ private function readPhpDocProperties($doc): void
}

try {
$phpDoc = Utils::createDocBlockInstance()->create($docComment);
$phpDoc = DocBlockFactory::createInstance()->create($docComment);

Choose a reason for hiding this comment

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

high

Consider using DocFactoryProvider::getDocFactory() instead to leverage the cached factory instance for better performance.

            $phpDoc = DocFactoryProvider::getDocFactory()->create($docComment);

@@ -76,7 +76,7 @@ public function readObjectFromPhpNode($node, $dummy = null): self
$docComment = $node->getDocComment();
if ($docComment) {
try {
$phpDoc = Utils::createDocBlockInstance()->create($docComment->getText());
$phpDoc = DocBlockFactory::createInstance()->create($docComment->getText());

Choose a reason for hiding this comment

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

high

Use DocFactoryProvider::getDocFactory() to utilize the cached factory instance, improving performance.

                $phpDoc = DocFactoryProvider::getDocFactory()->create($docComment->getText());

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: 5

🧹 Nitpick comments (1)
src/voku/SimplePhpParser/Model/PHPFunction.php (1)

231-235: Second occurrence – consider a cached factory

You create a new factory again here. After adding the import, this works, but repeatedly instantiating a factory is unnecessary.
Consider replacing both calls with the already-present DocFactoryProvider::getDocFactory() for consistency and less overhead.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 898f2c3 and 00f0c4b.

📒 Files selected for processing (6)
  • src/voku/SimplePhpParser/Model/PHPClass.php (2 hunks)
  • src/voku/SimplePhpParser/Model/PHPFunction.php (2 hunks)
  • src/voku/SimplePhpParser/Model/PHPMethod.php (1 hunks)
  • src/voku/SimplePhpParser/Model/PHPParameter.php (1 hunks)
  • src/voku/SimplePhpParser/Model/PHPProperty.php (1 hunks)
  • src/voku/SimplePhpParser/Model/PHPTrait.php (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Codacy Static Code Analysis
🔇 Additional comments (2)
src/voku/SimplePhpParser/Model/PHPClass.php (2)

7-8: Import looks good

DocBlockFactory is correctly imported and fully qualifies the class; no issues here.


389-390: Consistent factory usage

Nice job updating to DocBlockFactory::createInstance() here; once the other models add the missing import, all classes will be consistent.

Copy link

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.

1 participant