1. Checkout the issue queue for HAL and ReST.
2. Use the quickstart tool: https://github.com/build2be/drupal-rest-test.

Need HAL?

1. Install HAL Browser on your site to see what we got till now.

2. cd drupal-root

While working on Deploy RestWS for D7 project issue JSON I needed a pretty print for the node.json and scanner done for Drush Issue Queue Commands Fix for the new json structure on d.o D7. Both issues as still open so help needed.

Doing some research I learned about the PHP context or more specific the HTTP stream context

As we all know Drupal 8 has lots of new stuff. One of these items is based on Dependency Injection and result in a new file stored at sites/defaults/files/php/service_container/service_container_prod.php/e7000f005xxx.php and created very early during the bootstrap of Drupal. But what is it's contents?

Who is calling my function so many times? With devel module and some probing using debug_backtrace and a nifty by ref variable it's a snap.

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.

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.