sirian

@vodnicearv you wrong. Opera also built on top of chromium, but detects as `Opera` ``` Agent {#659 ▼ #cache: array:13 [▶] #userAgent: "Mozilla/5.0 (Macintosh; Intel Mac OS X 11_4) AppleWebKit/537.36...

it's possible to detect via `raw` value of template strings 

At this moment I prefer this: ``` namespace Foo\Entity; ... use Foo\Repository\ProductRepository; /** * @Entity(repositoryClass=ProductRepository::class) */ class Product { } ``` this works fine (I could even click on `repositoryClass=...`...

Ok... But still code could be optimized using array ``` var props = [ 'background-position-x', 'background-position-y', 'background-repeat-x', 'background-repeat-y', ... ]; for (let i = 0; i < props.length; i++) {...

@jsakas take a look at PR #105

@fatfisz @jsakas BTW. found another huge overhead - `coverage` dir. It takes 1.5MB. Is it necessary to include this dir in package? ``` bash-3.2$ npm install jsdom bash-3.2$ du -d...

> @sirian Good find, could you make a separate PR for that? Adding "lib" to "files" in `package.json` should do the job. https://github.com/jsdom/cssstyle/pull/106

> I honestly don't remember right now and for me it's not something super important, so I don't think we have to support IE. IMO we can just wait until...

same problem

As a workaround you could do reference priming manually. For example add BaseRepository class with method ``` public function primeReferences($items, $fields) { $dm = $this->getDocumentManager(); $primer = new ReferencePrimer($dm, $dm->getUnitOfWork());...