You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
bug #38867 [FrameworkBundle] Fixing TranslationUpdateCommand failure when using "--no-backup" (liarco)
This PR was squashed before being merged into the 5.1 branch.
Discussion
----------
[FrameworkBundle] Fixing TranslationUpdateCommand failure when using "--no-backup"
| Q | A
| ------------- | ---
| Branch? | 5.1
| Bug fix? | yes
| New feature? | no
| Deprecations? | no
| Tickets |
| License | MIT
| Doc PR |
[5.0.0](https://github.com/symfony/symfony/blob/5.0/src/Symfony/Component/Translation/CHANGELOG.md#500) removed `TranslationWriter::disableBackup()` but `TranslationUpdateCommand` still has `--no-backup` flag. Using that flag throws an error so I think that removing it without deprecation may be the right choice.
Thrown error:
```
In TranslationUpdateCommand.php line 287:
Attempted to call an undefined method named "disableBackup" of class "Symfony\Component\Translation\Writer\TranslationWriter".
```
Further references to the topic:
- #18290 (comment)
- #25860
Commits
-------
ef24b10 [FrameworkBundle] Fixing TranslationUpdateCommand failure when using "--no-backup"
0 commit comments