mirror of
https://github.com/silverstripe/silverstripe-cms
synced 2024-10-22 08:05:56 +02:00
bbc3aaaf9f
The main benefit of this is so that authors who make use of
.editorconfig don't end up with whitespace changes in their PRs.
Spaces vs. tabs has been left alone, although that could do with a
tidy-up in SS4 after the switch to PSR-1/2.
The command used was this:
for match in '*.ss' '*.css' '*.scss' '*.html' '*.yml' '*.php' '*.js' '*.csv' '*.inc' '*.php5'; do
find . -path ./thirdparty -prune -o -type f -name "$match" -exec sed -i '' 's/[[:space:]]\+$//' {} \+
find . -path ./thirdparty -prune -o -type f -name "$match" | xargs perl -pi -e 's/ +$//'
done
35 lines
1.0 KiB
PHP
35 lines
1.0 KiB
PHP
<?php
|
|
class ContentControllerSearchExtensionTest extends SapphireTest {
|
|
|
|
public function testCustomSearchFormClassesToTest() {
|
|
$page = new Page();
|
|
$page->URLSegment = 'whatever';
|
|
$page->Content = 'oh really?';
|
|
$page->write();
|
|
$page->publish('Stage', 'Live');
|
|
$controller = new ContentController($page);
|
|
$form = $controller->SearchForm();
|
|
|
|
if (get_class($form) == 'SearchForm') $this->assertEquals(array('File'), $form->getClassesToSearch());
|
|
}
|
|
|
|
public function setUpOnce() {
|
|
parent::setUpOnce();
|
|
|
|
FulltextSearchable::enable('File');
|
|
}
|
|
|
|
/**
|
|
* FulltextSearchable::enable() leaves behind remains that don't get cleaned up
|
|
* properly at the end of the test. This becomes apparent when a later test tries to
|
|
* ALTER TABLE File and add fulltext indexes with the InnoDB table type.
|
|
*/
|
|
public function tearDownOnce() {
|
|
parent::tearDownOnce();
|
|
|
|
Config::inst()->update('File', 'create_table_options', array('MySQLDatabase' => 'ENGINE=InnoDB'));
|
|
File::remove_extension('FulltextSearchable');
|
|
}
|
|
|
|
}
|