-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Impl/63469 rename restricted to internal comments #18669
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
Impl/63469 rename restricted to internal comments #18669
Conversation
7b303c5
to
e9899b6
Compare
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.
🥇 quite a chunky one, thanks for taking care of this @brunopagno !
lgtm, just left a few file renames that got left out. 👍🏾
@@ -123,6 +123,8 @@ class Journal < ApplicationRecord | |||
scope :for_work_package, -> { where(journable_type: "WorkPackage") } | |||
scope :for_meeting, -> { where(journable_type: "Meeting") } | |||
|
|||
alias_attribute :internal, :restricted |
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.
👍🏾
def rename_permissions(old, new) | ||
execute <<-SQL.squish | ||
UPDATE role_permissions | ||
SET permission = '#{new}' | ||
WHERE permission = '#{old}' | ||
SQL | ||
end |
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.
👍🏾 @machisuji should be happy 😉
eb9d0d2
to
d14e079
Compare
d14e079
to
fe708d5
Compare
Ticket
https://community.openproject.org/wp/63469
depends on https://github.com/opf/openproject-token/pull/22
What are you trying to accomplish?
Rename comments with restricted visibility to internal comments
What approach did you choose and why?
Renaming permissions, and strings, and internal representations. Risk of breaking things.