Question 1

How to add custom variables to PsyshBundle?

Accepted Answer

Configure custom variables in your Symfony config file under the 'psysh' key, referencing services with '@' prefix or parameters with '%', as shown in the README with examples like 'foo: bar' or 'router: "@router"'.

Question 2

PsyshBundle vs using PsySH directly in Symfony?

Accepted Answer

PsyshBundle provides out-of-the-box integration with Symfony, exposing services and parameters automatically, whereas using PsySH directly requires manual bootstrapping of the Symfony kernel and service container, making the bundle more convenient for Symfony-focused workflows.

Question 3

How to use PsyshBundle as a debugger for breakpoints?

Accepted Answer

Use the psysh() function within your code to drop into the interactive shell at specific points, passing variables like get_defined_vars() and $this for context, as demonstrated in the usage section of the README.

Question 4

Is PsyshBundle compatible with Symfony 6?

Accepted Answer

The README mentions support for Symfony >4.0 and automatic registration in Symfony 5, so it likely works with Symfony 6, but always check the latest package version or documentation for confirmed compatibility and any updates.

Question 5

How to add custom PsySH commands in Symfony using PsyshBundle?

Accepted Answer

Define a service class extending Psy\Command\Command or similar, then tag it with 'psysh.command' or rely on autoconfiguration in Symfony 3.3+, as outlined in the customization section of the README.

Question 6

Can I use PsyshBundle in production?

Accepted Answer

No, it's intended for development and test environments only, as interactive shells can expose security risks and are unnecessary in production; the README recommends installing it with '--dev' in Composer.

PsyshBundle

What is PsyshBundle?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions