Skip to content

Reproducer for parent as ID #1

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.

Sign up for GitHub

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

Jump to bottom
Open
deluxetom wants to merge 4 commits into
base: 2.x
Choose a base branch
from
Open

Reproducer for parent as ID #1

deluxetom wants to merge 4 commits into from

Conversation

@deluxetom
Copy link

@deluxetom deluxetom commented Oct 31, 2025

No description provided.

@gemini-code-assist
Copy link

gemini-code-assist bot commented Oct 31, 2025

Summary of Changes

Hello @deluxetom, 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 introduces a new test case to validate the behavior of zenstruck/foundry when dealing with a specific Doctrine ORM edge case: entities whose primary key is derived from a related parent entity's ID. The changes include defining the necessary entity structures and an integration test to ensure that the factory system can correctly create and manage these complex relationships.

Highlights

  • New Entity Definitions: Added two new Doctrine entities, InverseSide and OwningSide, to model a ManyToOne relationship where the OwningSide entity uses the InverseSide entity as part of its primary key, demonstrating a 'parent as ID' scenario.
  • Integration Test for Parent as ID: Introduced a new integration test (many_to_one_with_parent_as_id) in EdgeCasesRelationshipTest.php to verify that zenstruck/foundry correctly handles the creation and persistence of entities with this specific primary key configuration.
  • EntityManager Injection: The EdgeCasesRelationshipTest now includes a setUp method to inject the EntityManagerInterface, which is utilized in the new test case for entity retrieval.
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. ↩

gemini-code-assist[bot]

This comment was marked as outdated.

Sign in to view

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

1 more reviewer

@gemini-code-assist gemini-code-assist[bot] gemini-code-assist[bot] left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@deluxetom