Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
L
likvid
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Per Cederqvist
likvid
Commits
62f4bec5
Commit
62f4bec5
authored
18 years ago
by
Per Cederqvist
Browse files
Options
Downloads
Patches
Plain Diff
A Schedule has a RecurringItemRange, not a RecurringItem.
parent
e0d6581a
No related branches found
No related tags found
No related merge requests found
Changes
3
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
app/models/recurring_item.rb
+0
-1
0 additions, 1 deletion
app/models/recurring_item.rb
app/models/recurring_item_range.rb
+1
-0
1 addition, 0 deletions
app/models/recurring_item_range.rb
app/models/schedule.rb
+1
-1
1 addition, 1 deletion
app/models/schedule.rb
with
2 additions
and
2 deletions
app/models/recurring_item.rb
+
0
−
1
View file @
62f4bec5
class
RecurringItem
<
ActiveRecord
::
Base
belongs_to
:schedule
has_many
:recurring_item_ranges
end
This diff is collapsed.
Click to expand it.
app/models/recurring_item_range.rb
+
1
−
0
View file @
62f4bec5
class
RecurringItemRange
<
ActiveRecord
::
Base
belongs_to
:schedule
belongs_to
:recurring_item
end
This diff is collapsed.
Click to expand it.
app/models/schedule.rb
+
1
−
1
View file @
62f4bec5
class
Schedule
<
ActiveRecord
::
Base
has_many
:recurring_items
has_many
:recurring_item
_range
s
end
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment