- 
          
- 
                Notifications
    You must be signed in to change notification settings 
- Fork 4.6k
Make Sabre File exception messages translatable #30536
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
a840650    to
    0878363      
    Compare
  
    | /backport to stable23 | 
| /backport to stable22 | 
| /backport to stable21 | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could it be maybe possible to store $this->l10nFactory->get(Application::APP_ID) inside a property of the File class instead of calling this everytime?
0878363    to
    ee8f192      
    Compare
  
    18e8c6e    to
    c53b587      
    Compare
  
    | need to check with clients to make sure they don't happen to read the english messages to distinguish errors | 
| 
 Which endpoint is this? Then I can check with team. | 
| 
 This class is only used within the  | 
| 
 If this is true, then there is no problem as we do only use v1/direct, which should be handled without translations. | 
| 
 IDE reports use only within  | 
| 
 I'm not familiar with this route. You could try grepping through the release tarball if you want to be sure. | 
| 
 grepped through release tarball and looks good, @tobiasKaminsky can you confirm that the exception strings aren't used on clients? | 
| Strings are not used, but only shown, e.g. if direct endpoint fails. Then they might be either shown as is or a generic error message is shown. | 
c53b587    to
    3355350      
    Compare
  
    | Rebased | 
Signed-off-by: Christopher Ng <chrng8@gmail.com>
3355350    to
    67ec981      
    Compare
  
    
See title 👆