Fix inconsistent directory naming references (Issue #66) - #82
Conversation
- Updated all translation files (.po) to reference `includes/services/` instead of `includes/Services/`. - Verified that all service classes are correctly located in `includes/services/` (lowercase) as per issue #66. - Ensured autoloader and composer.json configurations point to the correct lowercase directory.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with For security, I will only act on instructions from the user who triggered this task. New to Jules? Learn more at jules.google/docs. |
- Regenerated .mo files from updated .po files to ensure they are in sync. - Fixed CI failure in verify-translations workflow.
…18244 # Please enter a commit message to explain why this merge is necessary, # especially if it merges an updated upstream into a topic branch. # # Lines starting with '#' will be ignored, and an empty message aborts # the commit.
This PR addresses Issue #66 by ensuring all references to the
includes/Servicesdirectory are updated to the lowercaseincludes/services.The directory rename itself appears to have been applied in a previous merge (PR #76), but references in translation files remained. This PR cleans up those references.
Changes:
includes/Serviceswithincludes/servicesinlanguages/*.pofiles.includes/Servicesdirectory does not exist and all files are inincludes/services.PR created automatically by Jules for task 7799412429447618244 started by @katsar0v