Shaun simshaun

"Push work down the tree"

One disadvantage of the top-down rendering approach we use is that the closer to the root of the application a component lives, the more it will be rerendered. The root component will be rerendered every time any data changes.

This is probably not a big deal for applications without much dynamic state, but let's say you have a input box at the bottom of a large tree of components (which will happen on pretty much any page containing a form). The user types, and every keystroke causes the entire app to rerender!

Well, this might be a big deal, or it might not be, depending on how you design your components. Some general guidelines will help us architect React apps that are fast by default, and don't need a whole lot of manual optimization.

HTML is work, components are placeholders

We needed to decide whether a user loaded from FOSUserBundle is granted a specific role. Because of the role hierarchy, this is not as simple as doing in_array($role, $user->getRoles()). The user model only knows about its roles, not about what other roles those roles grant it.

The only thing that handles this situation that i found is the SecurityContext::isGranted method. But the problem of that is that its a check about the role of the "current" user. We needed this information in a command that generates a file and needs to know which user has permission for a specific role.

The RoleHierarchy service can not do decisions but only explode roles into all roles granted through the tree. The RoleHiararchyVoter is part of the security manager. Both are private service and thus not intended to be reused in application code.

The simplest we could come up with is this code, which we use like this:

$roleHierarchy = $this->getContainer()->get('acme_demo.security.role_hierarchy_checker');

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

This tutorial as a series of videos

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

How to setup Git for Windows

I know this document seems long, but it shouldn't be too difficult to follow. This guide is based on Windows, but every program here has Linux/Mac equivalents, and in most cases they're built-in. So, take a deep breath and go step by step.

The steps below are for GitHub, but the steps are almost idential for Bitbucket, Heroku, etc.

You'll probably want to make sure Chocolatey is installed, since it streamlines installing this stuff later. If you install via Chocolatey, you don't need to run the installers from the products' respective sites.

	{
	"repositories": [
	{
	"type": "path",
	"url": "../relative/project/path"
	}
	],
	"require": {
	"${project}": "dev-${branch}"
	}

	class MoneyType extends AbstractType implements DataMapperInterface
	{
	public function buildForm(FormBuilder $builder, array $options)
	{
	$builder
	->add('amount', 'integer')
	->add('currency', 'string')
	->setDataMapper($this)
	;
	}

	[Console]::Beep(130, 100)
	[Console]::Beep(262, 100)
	[Console]::Beep(330, 100)
	[Console]::Beep(392, 100)
	[Console]::Beep(523, 100)
	[Console]::Beep(660, 100)
	[Console]::Beep(784, 300)
	[Console]::Beep(660, 300)
	[Console]::Beep(146, 100)
	[Console]::Beep(262, 100)

	<?php

	/**
	* This file is part of the Infinite SSO project.
	*
	* (c) Infinite Networks Pty Ltd <http://www.infinite.net.au>
	*
	* For the full copyright and license information, please view the LICENSE
	* file that was distributed with this source code.
	*/

	<?php

	namespace Acme\SecurityBundle\Role;

	use Symfony\Component\Security\Core\Role\RoleHierarchyInterface;
	use Symfony\Component\Security\Core\Role\RoleHierarchy;

	use Acme\SecurityBundle\Entity\RoleRepository;

	class DynamicRoleHierarchy implements RoleHierarchyInterface