I sometime need to check arrays for their values dispersed around. Just dumping the array is OK when interested in a particular key or value. But what about those big info arrays from hook_token_info, hook_menu etc. This is what I did.

How does the permission structure looks like for system.module? For this to visualize one needs to process system.routing.yml and

With Drupal 8 a lot is configured instead of programmed. So the key is to find out how it comes together. Graph API helps rendering these configurations.

Having a Drupal 8 site under development with a customer aware of the risk of loosing data I took the risk of fixing a broken Drupal 8 site. Today I did an code update and got the following welcome screen on http://drupal.dev

If you have just changed code (for example deployed a new module or moved an existing one) read http://drupal.org/documentation/rebuild
Additional uncaught exception thrown while handling exception.
Original

As a followup on A pinch of Symfony for D8MI? why do we need to squash?

After some more squash and push -f attempts regarding pull request for Symfony I get the hang of it.

But chx said in squash is bad as we loose history on the development process.

So how should we do this on d.o when git phase 3 lands? Those discussion seems to got to a halt.

For reviewing patches I try to use mostly http://drupal.org/project/drush_iq

Get latest code base

git checkout 8.x
git pull

Take an issue from the Issue Queue

Use the issue id or the issue id#comment to get a particular patch #

drush iq-apply-patch 1938158

Reinstall Drupal and work on the patch

Do what you have to do make Drupal work (again). And test or run tests

Change the patch and create a new one

diff 8.x > ~/Downloads/two-word-#nid-#comment.patch

Done

Trying to gra(s)p(h) Drupal\Tests\Core\Cache\BackendChainImplementationUnitTest

Trying to convert BlockStorageUnitTest to a real unit test. It seemed trival.

Below a graph generated from the module list of a Drupal 8 development site.