0

So, I'm looking for a solution for the following problem that would be "best practice" to implement in Symfony2.3.

Short description of situation: I've got a form defined in it's own class ("ProductType") The form contains a field that is linked to a different table. User needs to select 1 value from that list.

I want to restrict the values the user can choose from. Not all options that are found in the database are relevant. I need to dynamically reduce the options in the list based on information in the database and the current values already applied to the form. I can do this by adding a "Subscription" in which I change the contents of the form. But in this subscription I need access to the database/Doctrine Repository's to determine the list that the user may choose from.

So I need to inject Doctrine in the Subscription, but it is not available in the Type-class.

What is the best solution for this? - define the Subscription class as a service in Symfony and inject Doctrine via that route? - something else?

The Symfony documentation isn't very clear on this unfortunately.

DoppyNL
  • 1,415
  • 1
  • 14
  • 24

2 Answers2

0

i'm not sure if i got what you really want to do, but if you want to reduce a number of elements (insisde e.g dropdown) depends on value, use query builder for entity field type:

http://symfony.com/doc/current/reference/forms/types/entity.html#query-builder

Pawel
  • 1,672
  • 2
  • 18
  • 24
  • Correct, I will need the query builder to do just that. But to use the query builder, I need the repository. By default you don't have access to the repository's or the service locator in the Subscription class. I'm just checking to see if the right solution is to make the Subscription available via the ServiceLocator and injecting Doctrine via that route. When you need to do this, you may end up with a huge amount of services which I find a bit annoying. – DoppyNL May 31 '13 at 11:38
0

You need to use the query builder, so you need the repository. And to do so just use 

use Doctrine\ORM\EntityRepository;

in your ProductType, as it's explained in the doc

copndz
  • 1,104
  • 2
  • 12
  • 23
  • 1
    The problem was I needed to use the EntityRepository AND needed a value from the object the form was created for to adjust the result of that query. In the end you need to move the form element to a Subscriber so you have access to the form values and then pass one (or more) of those values via the closure to the EntityRepository. The combination of these 2 wasn't immediately obvious to me. But it is working like a charm now. – DoppyNL Jun 03 '13 at 08:17