Skip to content

Conversation

@yamadashy
Copy link
Owner

@yamadashy yamadashy commented Dec 1, 2025

Summary

  • Add explicit relativePathHelper: @relativePathHelper argument in extension.neon

related

Fixes #31

Some environments fail to autowire the relativePathHelper argument when
other arguments are explicitly specified. This adds the explicit argument
to ensure consistent DI resolution across all environments.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>
@gemini-code-assist
Copy link

Summary of Changes

Hello @yamadashy, 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 provides a critical fix for a dependency injection issue that caused service instantiation failures in specific environments. By explicitly defining all constructor arguments for the FriendlyErrorFormatter service within the Nette DI configuration, it ensures consistent and reliable dependency resolution, thereby preventing errors related to argument passing and improving overall stability.

Highlights

  • Dependency Injection Fix: Explicitly adds the relativePathHelper argument to the errorFormatter.friendly service definition in extension.neon to resolve a dependency injection error.
  • Environment Compatibility: Addresses an issue where Nette DI autowiring for relativePathHelper was inconsistent across different environments, leading to service instantiation failures after a recent upgrade.
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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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 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. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

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 configure Gemini 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 fixes a dependency injection error by explicitly defining the relativePathHelper argument in extension.neon. The change is correct and addresses the described issue. I've added one suggestion to also make the editorUrl argument explicit to fully align with the PR's goal and improve robustness.

@yamadashy yamadashy merged commit a8ce151 into main Dec 1, 2025
18 checks passed
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.

2 participants