Passed
Pull Request — master (#371)
by
unknown
61:13
created

Translatable::getFallbackLocale()   A

Complexity

Conditions 4
Paths 3

Size

Total Lines 10
Code Lines 5

Duplication

Lines 0
Ratio 0 %

Importance

Changes 0
Metric Value
dl 0
loc 10
c 0
b 0
f 0
rs 9.2
cc 4
eloc 5
nc 3
nop 1
1
<?php
2
3
namespace Dimsav\Translatable;
4
5
use App;
6
use Illuminate\Database\Eloquent\Model;
7
use Illuminate\Database\Eloquent\Builder;
8
use Illuminate\Database\Eloquent\Relations\Relation;
9
use Illuminate\Database\Query\Builder as QueryBuilder;
10
use Dimsav\Translatable\Exception\LocalesNotDefinedException;
11
12
trait Translatable
13
{
14
    protected $defaultLocale;
15
16
    /**
17
     * Alias for getTranslation().
18
     *
19
     * @param string|null $locale
20
     * @param bool        $withFallback
21
     *
22
     * @return \Illuminate\Database\Eloquent\Model|null
23
     */
24
    public function translate($locale = null, $withFallback = false)
25
    {
26
        return $this->getTranslation($locale, $withFallback);
27
    }
28
29
    /**
30
     * Alias for getTranslation().
31
     *
32
     * @param string $locale
33
     *
34
     * @return \Illuminate\Database\Eloquent\Model|null
35
     */
36
    public function translateOrDefault($locale)
37
    {
38
        return $this->getTranslation($locale, true);
39
    }
40
41
    /**
42
     * Alias for getTranslationOrNew().
43
     *
44
     * @param string $locale
45
     *
46
     * @return \Illuminate\Database\Eloquent\Model|null
47
     */
48
    public function translateOrNew($locale)
49
    {
50
        return $this->getTranslationOrNew($locale);
51
    }
52
53
    /**
54
     * @param string|null $locale
55
     * @param bool        $withFallback
56
     *
57
     * @return \Illuminate\Database\Eloquent\Model|null
58
     */
59
    public function getTranslation($locale = null, $withFallback = null)
60
    {
61
        $configFallbackLocale = $this->getFallbackLocale();
62
        $locale = $locale ?: $this->locale();
63
        $withFallback = $withFallback === null ? $this->useFallback() : $withFallback;
64
        $fallbackLocale = $this->getFallbackLocale($locale);
65
66
        if ($translation = $this->getTranslationByLocaleKey($locale)) {
67
            return $translation;
68
        }
69
        if ($withFallback && $fallbackLocale) {
70
            if ($translation = $this->getTranslationByLocaleKey($fallbackLocale)) {
71
                return $translation;
72
            }
73
            if ($translation = $this->getTranslationByLocaleKey($configFallbackLocale)) {
74
                return $translation;
75
            }
76
        }
77
78
        return null;
79
    }
80
81
    /**
82
     * @param string|null $locale
83
     *
84
     * @return bool
85
     */
86
    public function hasTranslation($locale = null)
87
    {
88
        $locale = $locale ?: $this->locale();
89
90
        foreach ($this->translations as $translation) {
0 ignored issues
show
Bug introduced by
The property translations does not exist. Did you maybe forget to declare it?

In PHP it is possible to write to properties without declaring them. For example, the following is perfectly valid PHP code:

class MyClass { }

$x = new MyClass();
$x->foo = true;

Generally, it is a good practice to explictly declare properties to avoid accidental typos and provide IDE auto-completion:

class MyClass {
    public $foo;
}

$x = new MyClass();
$x->foo = true;
Loading history...
91
            if ($translation->getAttribute($this->getLocaleKey()) == $locale) {
92
                return true;
93
            }
94
        }
95
96
        return false;
97
    }
98
99
    /**
100
     * @return string
101
     */
102
    public function getTranslationModelName()
103
    {
104
        return $this->translationModel ?: $this->getTranslationModelNameDefault();
0 ignored issues
show
Bug introduced by
The property translationModel does not exist. Did you maybe forget to declare it?

In PHP it is possible to write to properties without declaring them. For example, the following is perfectly valid PHP code:

class MyClass { }

$x = new MyClass();
$x->foo = true;

Generally, it is a good practice to explictly declare properties to avoid accidental typos and provide IDE auto-completion:

class MyClass {
    public $foo;
}

$x = new MyClass();
$x->foo = true;
Loading history...
105
    }
106
107
    /**
108
     * @return string
109
     */
110
    public function getTranslationModelNameDefault()
111
    {
112
        $config = app()->make('config');
113
114
        return get_class($this).$config->get('translatable.translation_suffix', 'Translation');
115
    }
116
117
    /**
118
     * @return string
119
     */
120
    public function getRelationKey()
121
    {
122
        if ($this->translationForeignKey) {
123
            $key = $this->translationForeignKey;
0 ignored issues
show
Bug introduced by
The property translationForeignKey does not exist. Did you maybe forget to declare it?

In PHP it is possible to write to properties without declaring them. For example, the following is perfectly valid PHP code:

class MyClass { }

$x = new MyClass();
$x->foo = true;

Generally, it is a good practice to explictly declare properties to avoid accidental typos and provide IDE auto-completion:

class MyClass {
    public $foo;
}

$x = new MyClass();
$x->foo = true;
Loading history...
124
        } elseif ($this->primaryKey !== 'id') {
0 ignored issues
show
Bug introduced by
The property primaryKey does not exist. Did you maybe forget to declare it?

In PHP it is possible to write to properties without declaring them. For example, the following is perfectly valid PHP code:

class MyClass { }

$x = new MyClass();
$x->foo = true;

Generally, it is a good practice to explictly declare properties to avoid accidental typos and provide IDE auto-completion:

class MyClass {
    public $foo;
}

$x = new MyClass();
$x->foo = true;
Loading history...
125
            $key = $this->primaryKey;
126
        } else {
127
            $key = $this->getForeignKey();
0 ignored issues
show
Bug introduced by
It seems like getForeignKey() must be provided by classes using this trait. How about adding it as abstract method to this trait?

This check looks for methods that are used by a trait but not required by it.

To illustrate, let’s look at the following code example

trait Idable {
    public function equalIds(Idable $other) {
        return $this->getId() === $other->getId();
    }
}

The trait Idable provides a method equalsId that in turn relies on the method getId(). If this method does not exist on a class mixing in this trait, the method will fail.

Adding the getId() as an abstract method to the trait will make sure it is available.

Loading history...
128
        }
129
130
        return $key;
131
    }
132
133
    /**
134
     * @return string
135
     */
136
    public function getLocaleKey()
137
    {
138
        $config = app()->make('config');
139
140
        return $this->localeKey ?: $config->get('translatable.locale_key', 'locale');
0 ignored issues
show
Bug introduced by
The property localeKey does not exist. Did you maybe forget to declare it?

In PHP it is possible to write to properties without declaring them. For example, the following is perfectly valid PHP code:

class MyClass { }

$x = new MyClass();
$x->foo = true;

Generally, it is a good practice to explictly declare properties to avoid accidental typos and provide IDE auto-completion:

class MyClass {
    public $foo;
}

$x = new MyClass();
$x->foo = true;
Loading history...
141
    }
142
143
    /**
144
     * @return \Illuminate\Database\Eloquent\Relations\HasMany
145
     */
146
    public function translations()
147
    {
148
        return $this->hasMany($this->getTranslationModelName(), $this->getRelationKey());
0 ignored issues
show
Bug introduced by
It seems like hasMany() must be provided by classes using this trait. How about adding it as abstract method to this trait?

This check looks for methods that are used by a trait but not required by it.

To illustrate, let’s look at the following code example

trait Idable {
    public function equalIds(Idable $other) {
        return $this->getId() === $other->getId();
    }
}

The trait Idable provides a method equalsId that in turn relies on the method getId(). If this method does not exist on a class mixing in this trait, the method will fail.

Adding the getId() as an abstract method to the trait will make sure it is available.

Loading history...
149
    }
150
151
    /**
152
     * @return bool
153
     */
154
    private function usePropertyFallback()
155
    {
156
        return app()->make('config')->get('translatable.use_property_fallback', false);
157
    }
158
159
    /**
160
     * Returns the attribute value from fallback translation if value of attribute
161
     * is empty and the property fallback is enabled in the configuration.
162
     * in model.
163
     * @param $locale
164
     * @param $attribute
165
     * @return mixed
166
     */
167
    private function getAttributeOrFallback($locale, $attribute)
168
    {
169
        $usePropertyFallback = $this->useFallback() && $this->usePropertyFallback();
170
        if (!$this->hasTranslation($locale) && $usePropertyFallback) {
171
            return $this->getTranslation($this->getFallbackLocale(), true)->$attribute;
172
        }
173
174
        return $this->getTranslation($locale)->$attribute;
175
    }
176
177
    /**
178
     * @param string $key
179
     *
180
     * @return mixed
181
     */
182
    public function getAttribute($key)
183
    {
184
        list($attribute, $locale) = $this->getAttributeAndLocale($key);
185
186
        if ($this->isTranslationAttribute($attribute)) {
187
            if ($this->getTranslation($locale) === null) {
188
                return null;
189
            }
190
191
            // If the given $attribute has a mutator, we push it to $attributes and then call getAttributeValue
192
            // on it. This way, we can use Eloquent's checking for Mutation, type casting, and
193
            // Date fields.
194
            if ($this->hasGetMutator($attribute)) {
0 ignored issues
show
Bug introduced by
It seems like hasGetMutator() must be provided by classes using this trait. How about adding it as abstract method to this trait?

This check looks for methods that are used by a trait but not required by it.

To illustrate, let’s look at the following code example

trait Idable {
    public function equalIds(Idable $other) {
        return $this->getId() === $other->getId();
    }
}

The trait Idable provides a method equalsId that in turn relies on the method getId(). If this method does not exist on a class mixing in this trait, the method will fail.

Adding the getId() as an abstract method to the trait will make sure it is available.

Loading history...
195
                $this->attributes[$attribute] = $this->getAttributeOrFallback($locale, $attribute);
0 ignored issues
show
Bug introduced by
The property attributes does not exist. Did you maybe forget to declare it?

In PHP it is possible to write to properties without declaring them. For example, the following is perfectly valid PHP code:

class MyClass { }

$x = new MyClass();
$x->foo = true;

Generally, it is a good practice to explictly declare properties to avoid accidental typos and provide IDE auto-completion:

class MyClass {
    public $foo;
}

$x = new MyClass();
$x->foo = true;
Loading history...
196
197
                return $this->getAttributeValue($attribute);
0 ignored issues
show
Bug introduced by
The method getAttributeValue() does not exist on Dimsav\Translatable\Translatable. Did you maybe mean getAttribute()?

This check marks calls to methods that do not seem to exist on an object.

This is most likely the result of a method being renamed without all references to it being renamed likewise.

Loading history...
198
            }
199
200
            return $this->getAttributeOrFallback($locale, $attribute);
201
        }
202
203
        return parent::getAttribute($key);
204
    }
205
206
    /**
207
     * @param string $key
208
     * @param mixed  $value
209
     *
210
     * @return $this
211
     */
212
    public function setAttribute($key, $value)
213
    {
214
        list($attribute, $locale) = $this->getAttributeAndLocale($key);
215
216
        if ($this->isTranslationAttribute($attribute)) {
217
            $this->getTranslationOrNew($locale)->$attribute = $value;
218
        } else {
219
            return parent::setAttribute($key, $value);
220
        }
221
222
        return $this;
223
    }
224
225
    /**
226
     * @param array $options
227
     *
228
     * @return bool
229
     */
230
    public function save(array $options = [])
231
    {
232
        if ($this->exists) {
0 ignored issues
show
Bug introduced by
The property exists does not exist. Did you maybe forget to declare it?

In PHP it is possible to write to properties without declaring them. For example, the following is perfectly valid PHP code:

class MyClass { }

$x = new MyClass();
$x->foo = true;

Generally, it is a good practice to explictly declare properties to avoid accidental typos and provide IDE auto-completion:

class MyClass {
    public $foo;
}

$x = new MyClass();
$x->foo = true;
Loading history...
233
            if (count($this->getDirty()) > 0) {
0 ignored issues
show
Bug introduced by
It seems like getDirty() must be provided by classes using this trait. How about adding it as abstract method to this trait?

This check looks for methods that are used by a trait but not required by it.

To illustrate, let’s look at the following code example

trait Idable {
    public function equalIds(Idable $other) {
        return $this->getId() === $other->getId();
    }
}

The trait Idable provides a method equalsId that in turn relies on the method getId(). If this method does not exist on a class mixing in this trait, the method will fail.

Adding the getId() as an abstract method to the trait will make sure it is available.

Loading history...
234
                // If $this->exists and dirty, parent::save() has to return true. If not,
0 ignored issues
show
Unused Code Comprehensibility introduced by
42% of this comment could be valid code. Did you maybe forget this after debugging?

Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it.

The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production.

This check looks for comments that seem to be mostly valid code and reports them.

Loading history...
235
                // an error has occurred. Therefore we shouldn't save the translations.
236
                if (parent::save($options)) {
237
                    return $this->saveTranslations();
238
                }
239
240
                return false;
241
            } else {
242
                // If $this->exists and not dirty, parent::save() skips saving and returns
0 ignored issues
show
Unused Code Comprehensibility introduced by
38% of this comment could be valid code. Did you maybe forget this after debugging?

Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it.

The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production.

This check looks for comments that seem to be mostly valid code and reports them.

Loading history...
243
                // false. So we have to save the translations
244
                if ($saved = $this->saveTranslations()) {
245
                    $this->fireModelEvent('saved', false);
0 ignored issues
show
Bug introduced by
It seems like fireModelEvent() must be provided by classes using this trait. How about adding it as abstract method to this trait?

This check looks for methods that are used by a trait but not required by it.

To illustrate, let’s look at the following code example

trait Idable {
    public function equalIds(Idable $other) {
        return $this->getId() === $other->getId();
    }
}

The trait Idable provides a method equalsId that in turn relies on the method getId(). If this method does not exist on a class mixing in this trait, the method will fail.

Adding the getId() as an abstract method to the trait will make sure it is available.

Loading history...
246
                    $this->fireModelEvent('updated', false);
0 ignored issues
show
Bug introduced by
It seems like fireModelEvent() must be provided by classes using this trait. How about adding it as abstract method to this trait?

This check looks for methods that are used by a trait but not required by it.

To illustrate, let’s look at the following code example

trait Idable {
    public function equalIds(Idable $other) {
        return $this->getId() === $other->getId();
    }
}

The trait Idable provides a method equalsId that in turn relies on the method getId(). If this method does not exist on a class mixing in this trait, the method will fail.

Adding the getId() as an abstract method to the trait will make sure it is available.

Loading history...
247
                }
248
249
                return $saved;
250
            }
251
        } elseif (parent::save($options)) {
252
            // We save the translations only if the instance is saved in the database.
253
            return $this->saveTranslations();
254
        }
255
256
        return false;
257
    }
258
259
    /**
260
     * @param string $locale
261
     *
262
     * @return \Illuminate\Database\Eloquent\Model|null
263
     */
264
    protected function getTranslationOrNew($locale)
265
    {
266
        if (($translation = $this->getTranslation($locale, false)) === null) {
267
            $translation = $this->getNewTranslation($locale);
268
        }
269
270
        return $translation;
271
    }
272
273
    /**
274
     * @param array $attributes
275
     *
276
     * @throws \Illuminate\Database\Eloquent\MassAssignmentException
277
     * @return $this
278
     */
279
    public function fill(array $attributes)
280
    {
281
        foreach ($attributes as $key => $values) {
282
            if ($this->isKeyALocale($key)) {
283
                $this->getTranslationOrNew($key)->fill($values);
284
                unset($attributes[$key]);
285
            } else {
286
                list($attribute, $locale) = $this->getAttributeAndLocale($key);
287
                if ($this->isTranslationAttribute($attribute) and $this->isKeyALocale($locale)) {
0 ignored issues
show
Comprehensibility Best Practice introduced by
Using logical operators such as and instead of && is generally not recommended.

PHP has two types of connecting operators (logical operators, and boolean operators):

  Logical Operators Boolean Operator
AND - meaning and &&
OR - meaning or ||

The difference between these is the order in which they are executed. In most cases, you would want to use a boolean operator like &&, or ||.

Let’s take a look at a few examples:

// Logical operators have lower precedence:
$f = false or true;

// is executed like this:
($f = false) or true;


// Boolean operators have higher precedence:
$f = false || true;

// is executed like this:
$f = (false || true);

Logical Operators are used for Control-Flow

One case where you explicitly want to use logical operators is for control-flow such as this:

$x === 5
    or die('$x must be 5.');

// Instead of
if ($x !== 5) {
    die('$x must be 5.');
}

Since die introduces problems of its own, f.e. it makes our code hardly testable, and prevents any kind of more sophisticated error handling; you probably do not want to use this in real-world code. Unfortunately, logical operators cannot be combined with throw at this point:

// The following is currently a parse error.
$x === 5
    or throw new RuntimeException('$x must be 5.');

These limitations lead to logical operators rarely being of use in current PHP code.

Loading history...
288
                    $this->getTranslationOrNew($locale)->fill([$attribute => $values]);
289
                    unset($attributes[$key]);
290
                }
291
            }
292
        }
293
294
        return parent::fill($attributes);
295
    }
296
297
    /**
298
     * @param string $key
299
     */
300
    private function getTranslationByLocaleKey($key)
301
    {
302
        foreach ($this->translations as $translation) {
303
            if ($translation->getAttribute($this->getLocaleKey()) == $key) {
304
                return $translation;
305
            }
306
        }
307
308
        return null;
309
    }
310
311
    /**
312
     * @param null $locale
313
     *
314
     * @return string
315
     */
316
    private function getFallbackLocale($locale = null)
317
    {
318
        if ($locale && $this->isLocaleCountryBased($locale)) {
319
            if ($fallback = $this->getLanguageFromCountryBasedLocale($locale)) {
320
                return $fallback;
321
            }
322
        }
323
324
        return app()->make('config')->get('translatable.fallback_locale');
325
    }
326
327
    /**
328
     * @param $locale
329
     *
330
     * @return bool
331
     */
332
    private function isLocaleCountryBased($locale)
333
    {
334
        return strpos($locale, $this->getLocaleSeparator()) !== false;
335
    }
336
337
    /**
338
     * @param $locale
339
     *
340
     * @return string
341
     */
342
    private function getLanguageFromCountryBasedLocale($locale)
343
    {
344
        $parts = explode($this->getLocaleSeparator(), $locale);
345
346
        return array_get($parts, 0);
347
    }
348
349
    /**
350
     * @return bool|null
351
     */
352
    private function useFallback()
353
    {
354
        if (isset($this->useTranslationFallback) && $this->useTranslationFallback !== null) {
355
            return $this->useTranslationFallback;
0 ignored issues
show
Bug introduced by
The property useTranslationFallback does not exist. Did you maybe forget to declare it?

In PHP it is possible to write to properties without declaring them. For example, the following is perfectly valid PHP code:

class MyClass { }

$x = new MyClass();
$x->foo = true;

Generally, it is a good practice to explictly declare properties to avoid accidental typos and provide IDE auto-completion:

class MyClass {
    public $foo;
}

$x = new MyClass();
$x->foo = true;
Loading history...
356
        }
357
358
        return app()->make('config')->get('translatable.use_fallback');
359
    }
360
361
    /**
362
     * @param string $key
363
     *
364
     * @return bool
365
     */
366
    public function isTranslationAttribute($key)
367
    {
368
        return in_array($key, $this->translatedAttributes);
0 ignored issues
show
Bug introduced by
The property translatedAttributes does not seem to exist. Did you mean attributes?

An attempt at access to an undefined property has been detected. This may either be a typographical error or the property has been renamed but there are still references to its old name.

If you really want to allow access to undefined properties, you can define magic methods to allow access. See the php core documentation on Overloading.

Loading history...
369
    }
370
371
    /**
372
     * @param string $key
373
     *
374
     * @throws \Dimsav\Translatable\Exception\LocalesNotDefinedException
375
     * @return bool
376
     */
377
    protected function isKeyALocale($key)
378
    {
379
        $locales = $this->getLocales();
380
381
        return in_array($key, $locales);
382
    }
383
384
    /**
385
     * @throws \Dimsav\Translatable\Exception\LocalesNotDefinedException
386
     * @return array
387
     */
388
    protected function getLocales()
389
    {
390
        $localesConfig = (array) app()->make('config')->get('translatable.locales');
391
392
        if (empty($localesConfig)) {
393
            throw new LocalesNotDefinedException('Please make sure you have run "php artisan config:publish dimsav/laravel-translatable" '.
394
                ' and that the locales configuration is defined.');
395
        }
396
397
        $locales = [];
398
        foreach ($localesConfig as $key => $locale) {
399
            if (is_array($locale)) {
400
                $locales[] = $key;
401
                foreach ($locale as $countryLocale) {
402
                    $locales[] = $key.$this->getLocaleSeparator().$countryLocale;
403
                }
404
            } else {
405
                $locales[] = $locale;
406
            }
407
        }
408
409
        return $locales;
410
    }
411
412
    /**
413
     * @return string
414
     */
415
    protected function getLocaleSeparator()
416
    {
417
        return app()->make('config')->get('translatable.locale_separator', '-');
418
    }
419
420
    /**
421
     * @return bool
422
     */
423
    protected function saveTranslations()
424
    {
425
        $saved = true;
426
        foreach ($this->translations as $translation) {
427
            if ($saved && $this->isTranslationDirty($translation)) {
428
                if (! empty($connectionName = $this->getConnectionName())) {
0 ignored issues
show
Bug introduced by
It seems like getConnectionName() must be provided by classes using this trait. How about adding it as abstract method to this trait?

This check looks for methods that are used by a trait but not required by it.

To illustrate, let’s look at the following code example

trait Idable {
    public function equalIds(Idable $other) {
        return $this->getId() === $other->getId();
    }
}

The trait Idable provides a method equalsId that in turn relies on the method getId(). If this method does not exist on a class mixing in this trait, the method will fail.

Adding the getId() as an abstract method to the trait will make sure it is available.

Loading history...
429
                    $translation->setConnection($connectionName);
430
                }
431
432
                $translation->setAttribute($this->getRelationKey(), $this->getKey());
0 ignored issues
show
Bug introduced by
It seems like getKey() must be provided by classes using this trait. How about adding it as abstract method to this trait?

This check looks for methods that are used by a trait but not required by it.

To illustrate, let’s look at the following code example

trait Idable {
    public function equalIds(Idable $other) {
        return $this->getId() === $other->getId();
    }
}

The trait Idable provides a method equalsId that in turn relies on the method getId(). If this method does not exist on a class mixing in this trait, the method will fail.

Adding the getId() as an abstract method to the trait will make sure it is available.

Loading history...
433
                $saved = $translation->save();
434
            }
435
        }
436
437
        return $saved;
438
    }
439
440
    /**
441
     * @param array
442
     *
443
     * @return \Illuminate\Database\Eloquent\Model
444
     */
445
    public function replicateWithTranslations(array $except = null)
446
    {
447
        $newInstance = parent::replicate($except);
0 ignored issues
show
Comprehensibility Bug introduced by
It seems like you call parent on a different method (replicate() instead of replicateWithTranslations()). Are you sure this is correct? If so, you might want to change this to $this->replicate().

This check looks for a call to a parent method whose name is different than the method from which it is called.

Consider the following code:

class Daddy
{
    protected function getFirstName()
    {
        return "Eidur";
    }

    protected function getSurName()
    {
        return "Gudjohnsen";
    }
}

class Son
{
    public function getFirstName()
    {
        return parent::getSurname();
    }
}

The getFirstName() method in the Son calls the wrong method in the parent class.

Loading history...
448
449
        unset($newInstance->translations);
450
        foreach ($this->translations as $translation) {
451
            $newTranslation = $translation->replicate();
452
            $newInstance->translations->add($newTranslation);
453
        }
454
455
        return  $newInstance;
456
    }
457
458
    /**
459
     * @param \Illuminate\Database\Eloquent\Model $translation
460
     *
461
     * @return bool
462
     */
463
    protected function isTranslationDirty(Model $translation)
464
    {
465
        $dirtyAttributes = $translation->getDirty();
466
        unset($dirtyAttributes[$this->getLocaleKey()]);
467
468
        return count($dirtyAttributes) > 0;
469
    }
470
471
    /**
472
     * @param string $locale
473
     *
474
     * @return \Illuminate\Database\Eloquent\Model
475
     */
476
    public function getNewTranslation($locale)
477
    {
478
        $modelName = $this->getTranslationModelName();
479
        $translation = new $modelName();
480
        $translation->setAttribute($this->getLocaleKey(), $locale);
481
        $this->translations->add($translation);
482
483
        return $translation;
484
    }
485
486
    /**
487
     * @param $key
488
     *
489
     * @return bool
490
     */
491
    public function __isset($key)
492
    {
493
        return $this->isTranslationAttribute($key) || parent::__isset($key);
494
    }
495
496
    /**
497
     * @param \Illuminate\Database\Eloquent\Builder $query
498
     * @param string                                $locale
499
     *
500
     * @return \Illuminate\Database\Eloquent\Builder|static
501
     */
502 View Code Duplication
    public function scopeTranslatedIn(Builder $query, $locale = null)
0 ignored issues
show
Duplication introduced by
This method seems to be duplicated in your project.

Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation.

You can also find more detailed suggestions in the “Code” section of your repository.

Loading history...
503
    {
504
        $locale = $locale ?: $this->locale();
505
506
        return $query->whereHas('translations', function (Builder $q) use ($locale) {
507
            $q->where($this->getLocaleKey(), '=', $locale);
508
        });
509
    }
510
511
    /**
512
     * @param \Illuminate\Database\Eloquent\Builder $query
513
     * @param string                                $locale
514
     *
515
     * @return \Illuminate\Database\Eloquent\Builder|static
516
     */
517 View Code Duplication
    public function scopeNotTranslatedIn(Builder $query, $locale = null)
0 ignored issues
show
Duplication introduced by
This method seems to be duplicated in your project.

Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation.

You can also find more detailed suggestions in the “Code” section of your repository.

Loading history...
518
    {
519
        $locale = $locale ?: $this->locale();
520
521
        return $query->whereDoesntHave('translations', function (Builder $q) use ($locale) {
522
            $q->where($this->getLocaleKey(), '=', $locale);
523
        });
524
    }
525
526
    /**
527
     * @param \Illuminate\Database\Eloquent\Builder $query
528
     *
529
     * @return \Illuminate\Database\Eloquent\Builder|static
530
     */
531
    public function scopeTranslated(Builder $query)
532
    {
533
        return $query->has('translations');
534
    }
535
536
    /**
537
     * Adds scope to get a list of translated attributes, using the current locale.
538
     * Example usage: Country::listsTranslations('name')->get()->toArray()
539
     * Will return an array with items:
540
     *  [
541
     *      'id' => '1',                // The id of country
542
     *      'name' => 'Griechenland'    // The translated name
543
     *  ].
544
     *
545
     * @param \Illuminate\Database\Eloquent\Builder $query
546
     * @param string                                $translationField
547
     */
548
    public function scopeListsTranslations(Builder $query, $translationField)
549
    {
550
        $withFallback = $this->useFallback();
551
        $translationTable = $this->getTranslationsTable();
552
        $localeKey = $this->getLocaleKey();
553
554
        $query
0 ignored issues
show
Bug introduced by
The method select() does not exist on Illuminate\Database\Eloquent\Builder. Did you maybe mean createSelectWithConstraint()?

This check marks calls to methods that do not seem to exist on an object.

This is most likely the result of a method being renamed without all references to it being renamed likewise.

Loading history...
555
            ->select($this->getTable().'.'.$this->getKeyName(), $translationTable.'.'.$translationField)
0 ignored issues
show
Bug introduced by
It seems like getTable() must be provided by classes using this trait. How about adding it as abstract method to this trait?

This check looks for methods that are used by a trait but not required by it.

To illustrate, let’s look at the following code example

trait Idable {
    public function equalIds(Idable $other) {
        return $this->getId() === $other->getId();
    }
}

The trait Idable provides a method equalsId that in turn relies on the method getId(). If this method does not exist on a class mixing in this trait, the method will fail.

Adding the getId() as an abstract method to the trait will make sure it is available.

Loading history...
Bug introduced by
It seems like getKeyName() must be provided by classes using this trait. How about adding it as abstract method to this trait?

This check looks for methods that are used by a trait but not required by it.

To illustrate, let’s look at the following code example

trait Idable {
    public function equalIds(Idable $other) {
        return $this->getId() === $other->getId();
    }
}

The trait Idable provides a method equalsId that in turn relies on the method getId(). If this method does not exist on a class mixing in this trait, the method will fail.

Adding the getId() as an abstract method to the trait will make sure it is available.

Loading history...
556
            ->leftJoin($translationTable, $translationTable.'.'.$this->getRelationKey(), '=', $this->getTable().'.'.$this->getKeyName())
0 ignored issues
show
Bug introduced by
It seems like getTable() must be provided by classes using this trait. How about adding it as abstract method to this trait?

This check looks for methods that are used by a trait but not required by it.

To illustrate, let’s look at the following code example

trait Idable {
    public function equalIds(Idable $other) {
        return $this->getId() === $other->getId();
    }
}

The trait Idable provides a method equalsId that in turn relies on the method getId(). If this method does not exist on a class mixing in this trait, the method will fail.

Adding the getId() as an abstract method to the trait will make sure it is available.

Loading history...
Bug introduced by
It seems like getKeyName() must be provided by classes using this trait. How about adding it as abstract method to this trait?

This check looks for methods that are used by a trait but not required by it.

To illustrate, let’s look at the following code example

trait Idable {
    public function equalIds(Idable $other) {
        return $this->getId() === $other->getId();
    }
}

The trait Idable provides a method equalsId that in turn relies on the method getId(). If this method does not exist on a class mixing in this trait, the method will fail.

Adding the getId() as an abstract method to the trait will make sure it is available.

Loading history...
557
            ->where($translationTable.'.'.$localeKey, $this->locale());
558
        if ($withFallback) {
559
            $query->orWhere(function (Builder $q) use ($translationTable, $localeKey) {
560
                $q->where($translationTable.'.'.$localeKey, $this->getFallbackLocale())
561
                  ->whereNotIn($translationTable.'.'.$this->getRelationKey(), function (QueryBuilder $q) use (
562
                      $translationTable,
563
                      $localeKey
564
                  ) {
565
                      $q->select($translationTable.'.'.$this->getRelationKey())
566
                        ->from($translationTable)
567
                        ->where($translationTable.'.'.$localeKey, $this->locale());
568
                  });
569
            });
570
        }
571
    }
572
573
    /**
574
     * This scope eager loads the translations for the default and the fallback locale only.
575
     * We can use this as a shortcut to improve performance in our application.
576
     *
577
     * @param Builder $query
578
     */
579
    public function scopeWithTranslation(Builder $query)
580
    {
581
        $query->with([
582
            'translations' => function (Relation $query) {
583
                $query->where($this->getTranslationsTable().'.'.$this->getLocaleKey(), $this->locale());
584
585
                if ($this->useFallback()) {
586
                    return $query->orWhere($this->getTranslationsTable().'.'.$this->getLocaleKey(), $this->getFallbackLocale());
587
                }
588
            },
589
        ]);
590
    }
591
592
    /**
593
     * This scope filters results by checking the translation fields.
594
     *
595
     * @param \Illuminate\Database\Eloquent\Builder $query
596
     * @param string                                $key
597
     * @param string                                $value
598
     * @param string                                $locale
599
     *
600
     * @return \Illuminate\Database\Eloquent\Builder|static
601
     */
602 View Code Duplication
    public function scopeWhereTranslation(Builder $query, $key, $value, $locale = null)
0 ignored issues
show
Duplication introduced by
This method seems to be duplicated in your project.

Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation.

You can also find more detailed suggestions in the “Code” section of your repository.

Loading history...
603
    {
604
        return $query->whereHas('translations', function (Builder $query) use ($key, $value, $locale) {
605
            $query->where($this->getTranslationsTable().'.'.$key, $value);
606
            if ($locale) {
0 ignored issues
show
Bug Best Practice introduced by
The expression $locale of type string|null is loosely compared to true; this is ambiguous if the string can be empty. You might want to explicitly use !== null instead.

In PHP, under loose comparison (like ==, or !=, or switch conditions), values of different types might be equal.

For string values, the empty string '' is a special case, in particular the following results might be unexpected:

''   == false // true
''   == null  // true
'ab' == false // false
'ab' == null  // false

// It is often better to use strict comparison
'' === false // false
'' === null  // false
Loading history...
607
                $query->where($this->getTranslationsTable().'.'.$this->getLocaleKey(), $locale);
608
            }
609
        });
610
    }
611
612
    /**
613
     * This scope filters results by checking the translation fields.
614
     *
615
     * @param \Illuminate\Database\Eloquent\Builder $query
616
     * @param string                                $key
617
     * @param string                                $value
618
     * @param string                                $locale
619
     *
620
     * @return \Illuminate\Database\Eloquent\Builder|static
621
     */
622
    public function scopeOrWhereTranslation(Builder $query, $key, $value, $locale = null)
623
    {
624
        return $query->orWhereHas('translations', function (Builder $query) use ($key, $value, $locale) {
625
            $query->where($this->getTranslationsTable().'.'.$key, $value);
626
            if ($locale) {
0 ignored issues
show
Bug Best Practice introduced by
The expression $locale of type string|null is loosely compared to true; this is ambiguous if the string can be empty. You might want to explicitly use !== null instead.

In PHP, under loose comparison (like ==, or !=, or switch conditions), values of different types might be equal.

For string values, the empty string '' is a special case, in particular the following results might be unexpected:

''   == false // true
''   == null  // true
'ab' == false // false
'ab' == null  // false

// It is often better to use strict comparison
'' === false // false
'' === null  // false
Loading history...
627
                $query->where($this->getTranslationsTable().'.'.$this->getLocaleKey(), $locale);
628
            }
629
        });
630
    }
631
632
    /**
633
     * This scope filters results by checking the translation fields.
634
     *
635
     * @param \Illuminate\Database\Eloquent\Builder $query
636
     * @param string                                $key
637
     * @param string                                $value
638
     * @param string                                $locale
639
     *
640
     * @return \Illuminate\Database\Eloquent\Builder|static
641
     */
642 View Code Duplication
    public function scopeWhereTranslationLike(Builder $query, $key, $value, $locale = null)
0 ignored issues
show
Duplication introduced by
This method seems to be duplicated in your project.

Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation.

You can also find more detailed suggestions in the “Code” section of your repository.

Loading history...
643
    {
644
        return $query->whereHas('translations', function (Builder $query) use ($key, $value, $locale) {
645
            $query->where($this->getTranslationsTable().'.'.$key, 'LIKE', $value);
646
            if ($locale) {
0 ignored issues
show
Bug Best Practice introduced by
The expression $locale of type string|null is loosely compared to true; this is ambiguous if the string can be empty. You might want to explicitly use !== null instead.

In PHP, under loose comparison (like ==, or !=, or switch conditions), values of different types might be equal.

For string values, the empty string '' is a special case, in particular the following results might be unexpected:

''   == false // true
''   == null  // true
'ab' == false // false
'ab' == null  // false

// It is often better to use strict comparison
'' === false // false
'' === null  // false
Loading history...
647
                $query->where($this->getTranslationsTable().'.'.$this->getLocaleKey(), 'LIKE', $locale);
648
            }
649
        });
650
    }
651
652
    /**
653
     * This scope filters results by checking the translation fields.
654
     *
655
     * @param \Illuminate\Database\Eloquent\Builder $query
656
     * @param string                                $key
657
     * @param string                                $value
658
     * @param string                                $locale
659
     *
660
     * @return \Illuminate\Database\Eloquent\Builder|static
661
     */
662
    public function scopeOrWhereTranslationLike(Builder $query, $key, $value, $locale = null)
663
    {
664
        return $query->orWhereHas('translations', function (Builder $query) use ($key, $value, $locale) {
665
            $query->where($this->getTranslationsTable().'.'.$key, 'LIKE', $value);
666
            if ($locale) {
0 ignored issues
show
Bug Best Practice introduced by
The expression $locale of type string|null is loosely compared to true; this is ambiguous if the string can be empty. You might want to explicitly use !== null instead.

In PHP, under loose comparison (like ==, or !=, or switch conditions), values of different types might be equal.

For string values, the empty string '' is a special case, in particular the following results might be unexpected:

''   == false // true
''   == null  // true
'ab' == false // false
'ab' == null  // false

// It is often better to use strict comparison
'' === false // false
'' === null  // false
Loading history...
667
                $query->where($this->getTranslationsTable().'.'.$this->getLocaleKey(), 'LIKE', $locale);
668
            }
669
        });
670
    }
671
672
    /**
673
     * @return array
674
     */
675
    public function attributesToArray()
676
    {
677
        $attributes = parent::attributesToArray();
678
679
        if (! $this->relationLoaded('translations') && ! $this->toArrayAlwaysLoadsTranslations()) {
0 ignored issues
show
Bug introduced by
It seems like relationLoaded() must be provided by classes using this trait. How about adding it as abstract method to this trait?

This check looks for methods that are used by a trait but not required by it.

To illustrate, let’s look at the following code example

trait Idable {
    public function equalIds(Idable $other) {
        return $this->getId() === $other->getId();
    }
}

The trait Idable provides a method equalsId that in turn relies on the method getId(). If this method does not exist on a class mixing in this trait, the method will fail.

Adding the getId() as an abstract method to the trait will make sure it is available.

Loading history...
680
            return $attributes;
681
        }
682
683
        $hiddenAttributes = $this->getHidden();
0 ignored issues
show
Bug introduced by
It seems like getHidden() must be provided by classes using this trait. How about adding it as abstract method to this trait?

This check looks for methods that are used by a trait but not required by it.

To illustrate, let’s look at the following code example

trait Idable {
    public function equalIds(Idable $other) {
        return $this->getId() === $other->getId();
    }
}

The trait Idable provides a method equalsId that in turn relies on the method getId(). If this method does not exist on a class mixing in this trait, the method will fail.

Adding the getId() as an abstract method to the trait will make sure it is available.

Loading history...
684
685
        foreach ($this->translatedAttributes as $field) {
0 ignored issues
show
Bug introduced by
The property translatedAttributes does not seem to exist. Did you mean attributes?

An attempt at access to an undefined property has been detected. This may either be a typographical error or the property has been renamed but there are still references to its old name.

If you really want to allow access to undefined properties, you can define magic methods to allow access. See the php core documentation on Overloading.

Loading history...
686
            if (in_array($field, $hiddenAttributes)) {
687
                continue;
688
            }
689
690
            if ($translations = $this->getTranslation()) {
0 ignored issues
show
Bug introduced by
Are you sure the assignment to $translations is correct as $this->getTranslation() (which targets Dimsav\Translatable\Translatable::getTranslation()) seems to always return null.

This check looks for function or method calls that always return null and whose return value is assigned to a variable.

class A
{
    function getObject()
    {
        return null;
    }

}

$a = new A();
$object = $a->getObject();

The method getObject() can return nothing but null, so it makes no sense to assign that value to a variable.

The reason is most likely that a function or method is imcomplete or has been reduced for debug purposes.

Loading history...
691
                $attributes[$field] = $translations->$field;
692
            }
693
        }
694
695
        return $attributes;
696
    }
697
698
    /**
699
     * @return array
700
     */
701
    public function getTranslationsArray()
702
    {
703
        $translations = [];
704
705
        foreach ($this->translations as $translation) {
706
            foreach ($this->translatedAttributes as $attr) {
0 ignored issues
show
Bug introduced by
The property translatedAttributes does not seem to exist. Did you mean attributes?

An attempt at access to an undefined property has been detected. This may either be a typographical error or the property has been renamed but there are still references to its old name.

If you really want to allow access to undefined properties, you can define magic methods to allow access. See the php core documentation on Overloading.

Loading history...
707
                $translations[$translation->{$this->getLocaleKey()}][$attr] = $translation->{$attr};
708
            }
709
        }
710
711
        return $translations;
712
    }
713
714
    /**
715
     * @return string
716
     */
717
    private function getTranslationsTable()
718
    {
719
        return app()->make($this->getTranslationModelName())->getTable();
720
    }
721
722
    /**
723
     * @return string
724
     */
725
    protected function locale()
726
    {
727
        if ($this->defaultLocale) {
728
            return $this->defaultLocale;
729
        }
730
731
        return app()->make('config')->get('translatable.locale')
732
            ?: app()->make('translator')->getLocale();
733
    }
734
735
    /**
736
     * Set the default locale on the model.
737
     *
738
     * @param $locale
739
     *
740
     * @return $this
741
     */
742
    public function setDefaultLocale($locale)
743
    {
744
        $this->defaultLocale = $locale;
745
746
        return $this;
747
    }
748
749
    /**
750
     * Get the default locale on the model.
751
     *
752
     * @return mixed
753
     */
754
    public function getDefaultLocale()
755
    {
756
        return $this->defaultLocale;
757
    }
758
759
    /**
760
     * Deletes all translations for this model.
761
     *
762
     * @param string|array|null $locales The locales to be deleted (array or single string)
763
     *                                   (e.g., ["en", "de"] would remove these translations).
764
     */
765
    public function deleteTranslations($locales = null)
766
    {
767
        if ($locales === null) {
768
            $translations = $this->translations()->get();
769
        } else {
770
            $locales = (array) $locales;
771
            $translations = $this->translations()->whereIn($this->getLocaleKey(), $locales)->get();
772
        }
773
        foreach ($translations as $translation) {
774
            $translation->delete();
775
        }
776
777
        // we need to manually "reload" the collection built from the relationship
778
        // otherwise $this->translations()->get() would NOT be the same as $this->translations
0 ignored issues
show
Unused Code Comprehensibility introduced by
36% of this comment could be valid code. Did you maybe forget this after debugging?

Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it.

The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production.

This check looks for comments that seem to be mostly valid code and reports them.

Loading history...
779
        $this->load('translations');
0 ignored issues
show
Bug introduced by
It seems like load() must be provided by classes using this trait. How about adding it as abstract method to this trait?

This check looks for methods that are used by a trait but not required by it.

To illustrate, let’s look at the following code example

trait Idable {
    public function equalIds(Idable $other) {
        return $this->getId() === $other->getId();
    }
}

The trait Idable provides a method equalsId that in turn relies on the method getId(). If this method does not exist on a class mixing in this trait, the method will fail.

Adding the getId() as an abstract method to the trait will make sure it is available.

Loading history...
780
    }
781
782
    /**
783
     * @param $key
784
     *
785
     * @return array
786
     */
787
    private function getAttributeAndLocale($key)
788
    {
789
        if (str_contains($key, ':')) {
790
            return explode(':', $key);
791
        }
792
793
        return [$key, $this->locale()];
794
    }
795
796
    /**
797
     * @return bool
798
     */
799
    private function toArrayAlwaysLoadsTranslations()
800
    {
801
        return app()->make('config')->get('translatable.to_array_always_loads_translations', true);
802
    }
803
}
804