Ever curious about what exactly is getting indexed in Solr? Drupal abstracts Solr to a point where it can be difficult to understand how Solr is queried directly. It's actually not that difficult.
If you find an error in your codebase, consider if the cause can be matched with a regular expression.
For example, consider a function that takes a variable as a reference, but is called with another function directly in it.
I'm working on an OO Primer series. This is a screencast on Interfaces.
I needed to implement "Add another" functionality on an entity form for a module I'm working on. The AJAX changes in D8 are subtle, but this was enough to derail me for a bit.
Objective: Show 1 text field on load. Provide a button that adds another text field with each click.
The dust is still settling in core, but I wanted to get PHPUnit running on my D8 custom modules. I'm not going to go into how to write tests here, just how to run tests.
My problem was that PHPUnit was running core tests just fine, but it wasn't picking up my custom module tests. Initially I had my tests in: modules/mymodule/lib/Drupal/mymodule/Tests
I looked around core a bit and moved them to a new directory: modules/mymodule/tests/Drupal/mymodule/Tests
When using annotation in D8 (e.g. when creating an entity), there are a couple classes annotation depends on. If you do not use them, you will get an exception that looks a little like this:
I've spent more time extending terminus, and thought it would be a good time to write a little more about it.
Terminus is an API/Drush integration project, by Pantheon. At its base is an API they have exposed to access information and execute workflow functionality you would otherwise only have access to via their dashboard. Drush wraps the API and provides the shell power make for some awesome command line tools.
It can be a pain for developers to setup a Solr instance for local development. Beyond the setup, there's the possibility for differences in configurations and versions. It's also entirely possible a developer could have multiple projects requiring different Solr versions and configurations. Whether you're a developer or devops engineer, adding Docker to your toolkit can ease this pain.
Chrome's network inspector allows you to filter by websocket connections so you can inspect raw websocket data.
All you need to do is open the inspector, click on "Network" and then click on "Websockets". From there, you can view the header info or "Frames", where you will ultimately see the data being sent to the browser.
I spent a little time working with Terminus due to a project that was recently moved over to Pantheon. Terminus is still very new, but the roadmap looks promising. This type of forward thinking is what's needed to comfortably integrate ops with managed services.
