github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-11 08:20:40 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

[PR #1320] [MERGED] fix(frontend): add missing permission translation keys #4887

New Issue
Closed
opened 2026-04-16 13:20:17 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-16 13:20:17 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/go-vikunja/vikunja/pull/1320
Author: @zapp88
Created: 8/20/2025
Status: ✅ Merged
Merged: 8/31/2025
Merged by: @kolaente

Base: main ← Head: main

📝 Commits (5)

  • 2d352ba fix(frontend): add missing permission translation keys
  • dc3d74a fix(frontend): improve Polish permission translations
  • 9818bca refactor(frontend): clean up permission translation structure
  • 960d8c5 fix(frontend): restore Polish permission translations
  • 8663dfb fix(frontend): correct Polish translation key from permission to right

📊 Changes

1 file changed (+1 additions, -1 deletions)

View changed files

📝 frontend/src/i18n/lang/en.json (+1 -1)

📄 Description

Added missing 'permission' section to both English and Polish translation files for project sharing permissions. This resolves the issue where permission labels were showing as raw keys (project.share.permission.readWrite) instead of translated text.

The permission section duplicates the existing 'right' section to maintain compatibility with components that reference either naming convention.

This PR fixes : https://github.com/go-vikunja/vikunja/issues/1319

The issue is resolved after fix :
obraz

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/go-vikunja/vikunja/pull/1320 **Author:** [@zapp88](https://github.com/zapp88) **Created:** 8/20/2025 **Status:** ✅ Merged **Merged:** 8/31/2025 **Merged by:** [@kolaente](https://github.com/kolaente) **Base:** `main` ← **Head:** `main` --- ### 📝 Commits (5) - [`2d352ba`](https://github.com/go-vikunja/vikunja/commit/2d352bacc8e2e4c2940d267923a460419b2b8e4e) fix(frontend): add missing permission translation keys - [`dc3d74a`](https://github.com/go-vikunja/vikunja/commit/dc3d74acc5c9a603355e4fb17b6f8411ff7624ef) fix(frontend): improve Polish permission translations - [`9818bca`](https://github.com/go-vikunja/vikunja/commit/9818bca80d085f8b9812ba8ba6c86fdbecf61c3f) refactor(frontend): clean up permission translation structure - [`960d8c5`](https://github.com/go-vikunja/vikunja/commit/960d8c544fdbd7ab3c5b087f86413bb79869b388) fix(frontend): restore Polish permission translations - [`8663dfb`](https://github.com/go-vikunja/vikunja/commit/8663dfb41b31d0313f8a98f59951e41a32c36089) fix(frontend): correct Polish translation key from permission to right ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `frontend/src/i18n/lang/en.json` (+1 -1) </details> ### 📄 Description Added missing 'permission' section to both English and Polish translation files for project sharing permissions. This resolves the issue where permission labels were showing as raw keys (project.share.permission.readWrite) instead of translated text. The permission section duplicates the existing 'right' section to maintain compatibility with components that reference either naming convention. This PR fixes : https://github.com/go-vikunja/vikunja/issues/1319 The issue is resolved after fix : <img width="796" height="157" alt="obraz" src="https://github.com/user-attachments/assets/606e05d8-73dd-4e1a-89e5-5fc86e9d50d8" /> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-16 13:20:17 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#4887
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?