Databases
StackOverflow2013
Postsdbo
POSymfony's choice list as ul in a view using twig
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSymfony's choice list as ul in a view using twig
    primarykey
    data
    text
    <p>I normally map user selectable properties to corresponding classes like so</p> <pre><code>class Person { /** * @ORM\ManyToMany(targetEntity="HobbyClass") */ private $hobby } class HobbyClass{ private $name; // e.g. "Outdoors" } </code></pre> <p>To create or edit entity I simply use entity type form field in the form. Then when I need to display the entity view with twig I just do this:</p> <pre><code> {% for item in person.hobby %} &lt;li&gt;{{ item.name }}&lt;/li&gt; {# e.g. "Outdoors" #} {% endfor %} </code></pre> <p>But this time I'm using class Selectables implementing ChoiceListInterface </p> <pre><code>class Entity { /** * @var array */ private $properties } class Selectables implements ChoiceListInterface { ... } </code></pre> <p>Then I create and edit this entity with choice type form field And of course in twig I get the keys, and not the names of the property like before</p> <pre><code> {% for item in entity.properties %} &lt;li&gt;{{ item }}&lt;/li&gt; {#e.g. "property_key", whereas its name is "Sports"#} {% endfor %} </code></pre> <p>The problem is that the data is just an array of keys that make sense only in a form. But I need to display it human readable in an entity view.</p> <p>The reason for using ChoiceListInterface is that the choice list is not going to be updated with CRUD and I can maintain it in code. It takes a little less effort to use and doesn't require a join and a db table.</p> <p>What would be the best possible solution to this:</p> <ul> <li>a. use tables and associations like before</li> <li>b. code custom twig extension which will get corresponding values from the ChoiceListInterface class</li> <li>c. use choice list and make keys translatable so they appear as property names</li> <li>d. anything else</li> </ul> <p>Thanks</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USuser608672
    1. USuser608672
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. POSymfony's choice list as ul in a view using twig
      1. This table or related slice is empty.
      1. VTDownMod
    2. VO
      singulars
      1. POSymfony's choice list as ul in a view using twig
      1. This table or related slice is empty.
      1. VTUpMod
    1. COdo you want to display `option` tags as a list? how? why? :)
      singulars
      1. POSymfony's choice list as ul in a view using twig
      1. USseferov
    2. COYes, I've created a complex entity which has a property mapped to an array. When I'm editing it in a form built with a choice field and rendered with corresponding widget it goes fine. But now I want to use a widget which will render an array as ul, extracting labels from a class implementing ChoiceListInterface. It's obviously missing and I have to code it myself. Before I do that I'm looking for a good example and it appears its not there. Post your code. I want to see how would you do that. Think of it as a preview of a blog post prior to posting it. I don't need checkboxes there.
      singulars
      1. POSymfony's choice list as ul in a view using twig
      1. USuser608672
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload