This repository has been archived by the owner on Jul 28, 2022. It is now read-only.
Force use existing translation strings in breadcrumb for Message entity #331
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jordisala1991
approved these changes
May 23, 2018
kunicmarko20
approved these changes
May 24, 2018
OskarStark
approved these changes
May 24, 2018
|
Thank you @covex-nn 👍 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I am targeting this branch, because this is BC patch.
See sonata-project/media-orm-pack#3, this PR solves similar issue
Changelog
Subject
If a last part of Message class name differs from
Message, thenAdminwill try to use non-existing translation string for breadcrumbs instead ofbreadcrumb.link_message_list, i.e. it will usebreadcrumb.link_sonata_notification_message_listforSonataNotificationMessage.With this PR
Adminwill be forced to use existing translation strings.