Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Jérome Perrin
gitlab-ce
Commits
e13d75c3
Commit
e13d75c3
authored
Jul 02, 2017
by
Bob Van Landuyt
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Explicitly define inverse of acces_level relations
parent
d964816b
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
7 additions
and
1 deletion
+7
-1
app/models/concerns/protected_ref.rb
app/models/concerns/protected_ref.rb
+7
-1
No files found.
app/models/concerns/protected_ref.rb
View file @
e13d75c3
...
...
@@ -17,7 +17,13 @@ module ProtectedRef
class_methods
do
def
protected_ref_access_levels
(
*
types
)
types
.
each
do
|
type
|
has_many
:"
#{
type
}
_access_levels"
,
dependent: :destroy
# rubocop:disable Cop/ActiveRecordDependent
# We need to set `inverse_of` to make sure the `belongs_to`-object is set
# when creating children using `accepts_nested_attributes_for`.
#
# If we don't `protected_branch` or `protected_tag` would be empty and
# `project` cannot be delegated to it, which in turn would cause validations
# to fail.
has_many
:"
#{
type
}
_access_levels"
,
dependent: :destroy
,
inverse_of:
self
.
model_name
.
singular
# rubocop:disable Cop/ActiveRecordDependent
validates
:"
#{
type
}
_access_levels"
,
length:
{
is:
1
,
message:
"are restricted to a single instance per
#{
self
.
model_name
.
human
}
."
}
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment