-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Rename LifeCycle to Project::LifeCycleStepDefinition and co #17248
base: feature/58159-fixed-set-of-project-stages-and-gates-editable-on-project-overview-page
Are you sure you want to change the base?
Conversation
…t::StageDefinition and Gate to Project::GateDefinition
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.
Nice, just few notes. Git rename detection for this PR makes files changed very confusing
@@ -1,5 +1,8 @@ | |||
class AddLifeCycleToWorkPackages < ActiveRecord::Migration[7.1] | |||
def change | |||
add_reference :work_packages, :project_life_cycle, foreign_key: true, null: true | |||
add_reference :work_packages, | |||
:life_cycle_step, |
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.
I think project_ life_cycle_step
should be more clear, though lengthier
If you change it foreign_key
can be just true
t.string :type | ||
t.string :name | ||
t.integer :position, default: 1, null: true |
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.
For ordering wherever they are listed?
t.date :start_date | ||
t.date :end_date | ||
t.boolean :active, default: false, null: false | ||
t.integer :position, default: 1, null: true |
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.
If this is for ordering when listing, then I think it should either follow the order of definitions or use start_date
Ticket
Part of https://community.openproject.org/wp/59287
What are you trying to accomplish?
Apply the class renamings discussed here: #17119 (comment) .
Merge checklist