As the title states, I am trying to add a custom property to the serialized object I return.
Let's take a User with the following methods:
getFirstname, setFirstname
getLastname, setLastname
getUsername, setUsername
...
Now in the serialization I would like to add a property fullName: Firstname + Lastname.
I have a getter method in my entity like so:
/**
* get name
*
* #return string
*/
public function getName()
{
return $this->getFirstname()." ".$this->getLastname();
}
My serialization file looks something like this:
AppBundle\Entity\User:
exclusion_policy: ALL
properties:
id:
expose: false
username:
expose: true
groups: [list, details]
email:
expose: true
groups: [details]
name:
expose: true
groups: [list, details]
I have tried with
name:
expose: true
groups: [list, details]
access_type: public_method
type: string
serialized_name: fullName
accessor:
getter: getName
and other variants but I can't seem to get it right.
Note: Yes I've cleared my cache and tried it again.
Anyone able to tell me what I am missing ?
Thanks in advance !
Since your full name is not a property at all you have to define a virtual property:
AppBundle\Entity\User:
exclusion_policy: ALL
properties:
# All properties but not name
virtual_properties:
getName:
groups: [list, details]
serialized_name: fullName
Related
in config.yml
edit:
title: 'editing %firstname% '
fields:
- {property: firstname, type: string}
- {property: lastname, type: string}
- {property: email, type: string}
- {property: password,type: password}
- {property: mobilenumber, type: string}
- enabled
i want the username to come up dynamically and %firstname% doesn't work.
You can only display entity ID in edit view like this:
title: 'editing %%entity_id%%'
Starting from there, you can use Doctrine composite primary key to include firstname (or username?) in your primary key on User class:
/** #ORM\Id #ORM\Column(type="string") */
private $username;
I am working with a bundle called rss-atom-bundle. Through this bundle I should be able to fetch the RSS feeds and save them to the database.
I can get the bundle to work up till getting the feeds from the URL but when I try to presist I get the following error and I just cant figure it out why I am getting it.
The class 'Debril\RssAtomBundle\Protocol\Parser\Item' was not found in the chain configured namespaces Symfony\Bundle\AsseticBundle\Entity, AppBundle\Entity`
Looking online and at stackoverflow i came across questions that were related to this but all of them are talking about by default the Entity should be inside the Entity folder of the Bundle and if they are not then this error appears but my Entity files are inside Entity folder and I followed the instructions given by the bundle author but still i cant get passed this error
This is what my Controller looks like
$em = $this->getDoctrine()->getManager();
// fetch the FeedReader
$reader = $this->container->get('debril.reader');
// this date is used to fetch only the latest items
$unmodifiedSince = '01/01/2000';
$date = new \DateTime($unmodifiedSince);
// the feed you want to read
$url = 'http://example.com/feed/';
$feeds = $reader->getFeedContent($url, $date);
$items = $feeds->getItems();
dump($items);
foreach ( $items as $item ) {
$em->persist($item);
}
$em->flush();
As per bundle instructions I did implement FeedInterface to my Feed Entity and ItemInInterface, ItemOutInterface to my Item Entity
This is what my orm.yml looks like for Feed and Item Entity
Feed
AppBundle\Entity\Feed:
type: entity
table: null
id:
id:
type: integer
id: true
generator:
strategy: AUTO
fields:
title:
type: string
length: 255
description:
type: text
link:
type: text
publicId:
type: text
lastModified:
type: datetime
lastViewed:
type: datetime
oneToMany:
items:
targetEntity: AppBundle\Entity\Item
mappedBy: feed
cascade: ["persist"]
lifecycleCallbacks: { }
Item
AppBundle\Entity\Item:
type: entity
table: null
id:
id:
type: integer
id: true
generator:
strategy: AUTO
fields:
title:
type: string
length: 255
title:
type: text
nullable: true
summary:
type: text
nullable: true
description:
type: text
nullable: true
medias:
type: text
nullable: true
updated:
type: string
nullable: true
publicId:
type: string
nullable: true
link:
type: string
nullable: true
comment:
type: string
nullable: true
author:
type: string
nullable: true
manyToOne:
feed:
targetEntity: AppBundle\Entity\Feed
inversedBy: items
joinColumn:
name: feed_id
referencedColumnName: id
Any help will be really appreciated as I am clueless why i am getting the error?
Try to add RssAtomBundle to the list with mappings in app/config/config.yml
orm:
entity_managers:
default:
connection: default
mappings:
AppBundle: ~
AsseticBundle: ~
RssAtomBundle: ~
My title might not be the best description, but it's best I could come up with.
I have 4 entities; Page, PageElement, Image and an entity called TextWithImage. Page holds pageElements (array of PageElement entities). Those pageElements can be of numerous types, but for now I have only one called TextWithImage that's holding additional data to the data the PageElement entity holds.
The PageElement can be included on numerous pages and so, I have a ManyToMany in the PageElement.orm.yml. The TextWithImage has a manyToOne to reference to Image.
(More information: Another Entity ImageGallery might have a manyToMany relationship with the Image entity, while TextOnly shouldn't have any reference to the Image entity.)
I want to be able to get the Page and retrieve the PageElements with all their "attributes". So let's say I request to get a Page with only one TextWithImage type of PageElement, I want to return the following.
Page -> pageElements = array (
[0] => TextWithImage -> image = Image -> filename = "image.png"
-> alt = "An image!"
-> text = "There's an image too!"
)
All seems simple enough, but I need doctrine to understand that this PageElement is a TextWithImage type. Can I do this with a DiscriminatorColumn, say (rough sketch);
Table: pageelement
id | attributes | discr | TextWithImageId
Table: textwithimage
id | attributes
Keep in mind that I'll have more than just one type of PageElement, not only TextWithImage.
Is this possible and if so, how?
I've found the solution to my problem. These are the doctrine YML files. You can generate all entities with php app/console doctrine:generate:entities AppBundle/Entity. Make sure that the PageTextImageElement class extends the PageElement class.
Page.orm.yml
AppBundle\Entity\Page:
type: entity
table: null
repositoryClass: AppBundle\Repositories\PageRepository
manyToMany:
pageElements:
targetEntity: PageElement
cascade: ["all"]
joinTable:
name: null
joinColumns:
page_id:
referencedColumnName: id
onDelete: CASCADE
inverseJoinColumns:
page_element_id:
referencedColumnName: id
unique: true
onDelete: CASCADE
id:
id:
type: integer
id: true
generator:
strategy: AUTO
fields:
name:
type: string
length: '255'
unique: true
lifecycleCallbacks: { }
PageElement.orm.yml
AppBundle\Entity\PageElement:
type: entity
inheritanceType: SINGLE_TABLE
discriminatorColumn:
name: discr
type: string
discriminatorMap:
pageTextImageElement: PageTextImageElement
table: null
repositoryClass: AppBundle\Repositories\PageElementRepository
id:
id:
type: integer
id: true
generator:
strategy: AUTO
fields:
sortOrder:
type: integer
attributes:
type: array
nullable: true
lifecycleCallbacks: { }
PageTextImageElement.orm.yml
AppBundle\Entity\PageTextImageElement:
type: entity
table: null
oneToOne:
image:
targetEntity: AppBundle\Entity\Image
joinColumn:
name: imageId
referencedColumnName: id
fields:
passage:
type: string
length: '255'
lifecycleCallbacks: { }
Image.orm.yml
AppBundle\Entity\Image:
type: entity
table: null
repositoryClass: AppBundle\Repositories\ImageRepository
id:
id:
type: integer
id: true
generator:
strategy: AUTO
fields:
name:
type: string
length: '255'
unique: true
description:
type: string
length: '255'
lifecycleCallbacks: { }
I'm not really familiar with YAML so I open parameters.yml and config.yml files to see example how to use parameters or variable in YAML.
parameters.yml:
parameters:
database_driver: pdo_mysql
database_host: 127.0.0.1
database_port: 3306
database_name: homlist
config.yml:
doctrine:
dbal:
driver: "%database_driver%"
host: "%database_host%"
port: "%database_port%"
dbname: "%database_name%"
But when I tried it with doctrine mapping yaml file like this:
parameters:
table_name: test
Mockizart\Bundle\BlogBundle\Entity\MockblogTag:
type: entity
table: "%table_name%"
it's error like this:
An exception occurred while executing 'SELECT count(DISTINCT %0_.id) AS sclr0 FROM %table_name% %0_':
this is my mapping file Resources\Config\Entity\MockblogTag
Mockizart\Bundle\BlogBundle\Entity\MockblogTag:
type: entity
table: mockblog_tag
indexes:
user_id:
columns:
- user_id
name:
columns:
- name
slug:
columns:
- slug
id:
id:
type: integer
nullable: false
unsigned: false
comment: ''
id: true
generator:
strategy: IDENTITY
fields:
dateCreated:
type: integer
nullable: false
unsigned: false
comment: ''
column: date_created
name:
type: string
nullable: false
length: 60
fixed: false
comment: ''
slug:
type: string
nullable: false
length: 100
fixed: false
comment: ''
totalPost:
type: integer
nullable: false
unsigned: false
comment: ''
column: total_post
manyToOne:
user:
targetEntity: ORD\UserBundle\Entity\User
joinColumn:
referencedColumnName: id
type: integer
nullable: false
unsigned: false
lifecycleCallbacks:
How to define variable in yaml symfony2 ?
The way of defining parameters it's correct, however I see from comments that your purpose is to configure the class used for User object:
As Cerad said you can't do that. But if you want to configure the class you use for the User, you can have a manager service class.
<?php
namespace YourNamespace\UserBundle\Manager;
use Doctrine\Common\Persistence\ObjectManager;
class UserManager
{
/**
* #var ObjectManager
*/
protected $em;
/**
* Your user class
*
* #var string
*/
protected $className;
public function __construct(ObjectManager $em, $class)
{
$this->em = $em;
$this->className = $class;
}
public function createInstance()
{
return new $this->className;
}
public function getRepository()
{
return $this->em->getRepository($this->className);
}
}
And the services definitions will be like this:
services:
your_user.manager:
class: YourNamespace\UserBundle\Manager\UserManager
arguments: ['#doctrine.orm.entity_manager', 'YourNamespace\UserBundle\Entity\User']
In your controller you can use this manager class like this:
$userManager = $this->get('your_user.manager');
$user = $userManager->createInstance();
I think this is a good way to have a central point when dealing with user object. And if someday for whatever reason you decide to use a different class for user you just modify the argument 'YourNamespace\UserBundle\Entity\User'.
Also in this way you can use 'YourNamespace\UserBundle\Entity\User' argument as parameter, so the definition will change to:
services:
your_user.manager:
class: Moneytablet\UserBundle\Manager\UserManager
arguments: ['#doctrine.orm.entity_manager', '%user_class%']
and in you parameters.yml you can have:
parameters:
user_class: YouNamespace\UserBundle\Entity\User
I really like working this way, you can create save(), remove() methods on manager class and so on. Also later on when creating new services you can inject this manager like a regular service if it's a dependency.
And if you want a new manager for a different entity, you can create a new service definition with different construct arguments, but with the same service class.
I have a Product entity, and a ProductList entity.
Is it possible to serialize (and deserialize) a ProductList object to json in a way that the json contains the Product objects related to that ProductList?
The expected output is:
[{
'product_list_name': 'List',
'product_list_created': '2013-07-04',
'products' : {
'product': {...},
'product': {...},
'product': {...},
'product': {...}
}]
I'm using the Symfony2 built-in serializer and JMS\Serializer but I am not having any luck.
Any way to do this?
If you are using YML, ensure you have a YML file for both Product and ProductList.
Entity.ProductList.yml
AppBundle\Entity\ProductList:
exclusion_policy: ALL
properties:
products:
expose: true
Entity.Product.yml
AppBundle\Entity\Product:
exclusion_policy: ALL
properties:
id:
expose: true