documentation-developer
documentation-developer copied to clipboard
Fix bazinga usage
| Question | Answer |
|---|---|
| JIRA Ticket | |
| Versions | |
| Edition |
bazinga must generate the translations in the ./public/assets directory, not the ./assets directory.
It also means that removing ./assets doesn't remove translations.
composer run post-update-cmd is clearing the cache, and is running bazinga and yarn. It's the best way to get the translations working.
See composer.json script using bazinga:js-translation:dump %PUBLIC_DIR%/assets --merge-domains: https://github.com/ibexa/recipes/blob/master/ibexa/oss/4.6/manifest.json#L94
Checklist
- [ ] Text renders correctly
- [ ] Text has been checked with vale
- [ ] Description metadata is up to date
- [ ] Redirects cover removed/moved pages
- [ ] Code samples are working
- [ ] PHP code samples have been fixed with PHP CS fixer
- [ ] Added link to this PR in relevant JIRA ticket or code PR