From d9cf71b91bbc086ee3b9d3bf48f4d38d7c6002f4 Mon Sep 17 00:00:00 2001
From: Ingo Schommer <ingo@silverstripe.com>
Date: Thu, 19 May 2016 12:46:56 +1200
Subject: [PATCH] Consistently add Locale to test fixtures (fixes #223)

Technically this should be fixed by changing the logic
in Translatable::get_extra_config(), which modifies the 'defaults'
configuration on the objects it applies to. Since this is called
very early during the configuration bootstrap, it sets whatever
the current value of Translatable::get_default_locale() is there.
Any changes at a later time don't affect newly created objects,
even Translatable::reset() doesn't alter the initially configured 'defaults'.
---
 tests/unit/TranslatableTest.yml | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/tests/unit/TranslatableTest.yml b/tests/unit/TranslatableTest.yml
index 43707e4..e7a723d 100644
--- a/tests/unit/TranslatableTest.yml
+++ b/tests/unit/TranslatableTest.yml
@@ -16,26 +16,32 @@ Page:
    parent:
       Title: Parent
       URLSegment: parent
+      Locale: en_US
    child1:
       Title: Child 1
       URLSegment: child1
       Parent: =>Page.parent
+      Locale: en_US
    child2:
       Title: Child 2
       URLSegment: child2
       Parent: =>Page.parent
+      Locale: en_US
    child3:
       Title: Child 3
       URLSegment: child3
       Parent: =>Page.parent
+      Locale: en_US
    grandchild1:
       Title: Grandchild
       URLSegment: grandchild1
       Parent: =>Page.child1
+      Locale: en_US
    grandchild2:
       Title: Grandchild
       URLSegment: grandchild2
       Parent: =>Page.child1
+      Locale: en_US
 TranslatableTest_DataObject:
    testobject_en:
       TranslatableProperty: en_US