This would fix #83?

@westonruter Yes, it would fix also #83.

Are you OK with the general idea of recommending Composer and npm install instead of the git submodules?

Yes, I'm probably just old fashioned for still clinging to what is familiar to me.

OK, this is super strange. It is actually failing during WP_UnitTestCase::tearDownAfterClass() when it calls _delete_all_data():

function _delete_all_data() {
	global $wpdb;

	foreach ( array(
		$wpdb->posts,
		$wpdb->postmeta,
		$wpdb->comments,
		$wpdb->commentmeta,
		$wpdb->term_relationships,
		$wpdb->termmeta,
	) as $table ) {
		$wpdb->query( "DELETE FROM {$table}" );
	}

	foreach ( array(
		$wpdb->terms,
		$wpdb->term_taxonomy,
	) as $table ) {
		$wpdb->query( "DELETE FROM {$table} WHERE term_id != 1" );
	}

	$wpdb->query( "UPDATE {$wpdb->term_taxonomy} SET count = 0" );

	$wpdb->query( "DELETE FROM {$wpdb->users} WHERE ID != 1" );
	$wpdb->query( "DELETE FROM {$wpdb->usermeta} WHERE user_id != 1" );
}

while doing any queries during the actual tests works just fine.

@kasparsd How close is this to being done? I'm working on an updated version of the wp-foo-bar plugin that is using this branch and I'd like to merge this PR before merging the other. What is outstanding or needs review?

@valendesigns I think it is pretty much done. Will look into resolving the merge conflicts.

Could you please check the updated readme copy and ensure it sounds good and clear?

@westonruter This is ready for another round of code review.

I've tagged a 0.1.0 release to ensure users can always revert to the previous version.

It's working well in my testing of the composer method: ampproject/amp-wp#1131

@kasparsd would you tag a new release? I'm guessing that would be 0.2.0? We'll then use that in the AMP plugin.

@westonruter I tagged it as 1.0.0 as this is a breaking change since files have been moved around.