Skip to content

Add missing symfony/property-access dependency - #47

Merged
ddebowczyk merged 2 commits into
cognesy:mainfrom
jackwh:patch-1
Sep 18, 2025
Merged

Add missing symfony/property-access dependency#47
ddebowczyk merged 2 commits into
cognesy:mainfrom
jackwh:patch-1

Conversation

@jackwh

@jackwh jackwh commented Aug 24, 2025

Copy link
Copy Markdown
Contributor

Hi there! I just installed Instructor and was experimenting with the Ollama example in the docs.

The example wouldn't run due to Class "Symfony\Component\PropertyAccess\PropertyAccess" not found.

Running composer require symfony/property-access fixed it and now it works perfectly, so this PR just adds the missing dependency in to composer.json.

Thanks for an incredible package! 🙏

Summary by CodeRabbit

  • Chores
    • Updated dependencies to improve compatibility and maintainability; no functional changes to features.
    • Enhances compatibility with current and upcoming framework versions.
    • Installation and build processes are more reliable.
    • No user-facing changes; no action required.
    • Release focuses on underlying package management updates only.
    • Existing workflows, settings, and data remain unaffected.

@coderabbitai

coderabbitai Bot commented Aug 24, 2025

Copy link
Copy Markdown
Contributor

Walkthrough

Added a new Composer dependency: symfony/property-access with version constraint ^6.4|^7.0 in composer.json’s require section.

Changes

Cohort / File(s) Summary
Dependency addition
composer.json
Added symfony/property-access to require with version `^6.4

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I twitch my whiskers, dependencies align,
A property path now neatly defined.
With Symfony’s access I hop through arrays,
Fields and objects in tidy displays.
Thump-thump—composer hums, all set to go,
A carrot of order in the data flow. 🥕

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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
🪧 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.
    • 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.
  • 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

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

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • 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.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (2)
composer.json (2)

143-143: Optional: align Symfony constraint style for consistency.

The require section mixes constraint formats (e.g., "^6.4|^7.1", "^6.4|^7.0", and "^6.4 || ^7.0"). Consider standardizing the style in a follow-up (not blocking). Keeping "^6.4|^7.0" here is fine.


143-143: Add a tiny smoke test to prevent regressions.

A minimal test that instantiates the accessor would guard against accidental removal of the dependency and ensure the runtime path is exercised.

Example Pest test (place under packages/instructor/tests or examples’ tests):

<?php

use Symfony\Component\PropertyAccess\PropertyAccess;
use Symfony\Component\PropertyAccess\PropertyAccessorInterface;

it('can create a Symfony PropertyAccessor', function () {
    $pa = PropertyAccess::createPropertyAccessor();
    expect($pa)->toBeInstanceOf(PropertyAccessorInterface::class);
});

I can open a follow-up PR adding this smoke test if you prefer.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 8a1e2d6 and c1cc545.

📒 Files selected for processing (1)
  • composer.json (1 hunks)
🔇 Additional comments (2)
composer.json (2)

143-143: Fix missing runtime dependency for PropertyAccess — good catch.

Adding symfony/property-access resolves the "Class 'Symfony\Component\PropertyAccess\PropertyAccess' not found" error users hit when running the Ollama example. The constraint (^6.4|^7.0) is compatible with the rest of the Symfony stack in this repo and will resolve to 7.x given other requirements.


143-143: Please re-run the Ollama example end-to-end on a clean install.

To verify the user-reported scenario is fully addressed, run a fresh clone + composer install and execute the Ollama example from the docs, ensuring no other missing packages surface.

@ddebowczyk

Copy link
Copy Markdown
Contributor

Hey, property access is not included intentionally as Instructor works with 6.x and 7.x versions and some users still rely on 6.x.
You can include required version in your solution.
Am I missing something?

@ddebowczyk
ddebowczyk merged commit 6b0a738 into cognesy:main Sep 18, 2025
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