-
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
Feature/58163 project specific stage administration #17200
Feature/58163 project specific stage administration #17200
Conversation
6775f44
to
63f8af7
Compare
4a407ed
to
79c25d6
Compare
79c25d6
to
c791037
Compare
f829684
to
c485739
Compare
c791037
to
36b37a4
Compare
12f662e
to
dc71f0b
Compare
Non existing mappings between project and step definition will be created on the fly.
The failing feature specs are flickering and weren't broken by the changes within this PR. |
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.
Looks good, mostly minor notes
app/components/projects/settings/life_cycles/show_page_header_component.html.erb
Outdated
Show resolved
Hide resolved
app/components/projects/settings/life_cycles/show_page_header_component.html.erb
Outdated
Show resolved
Hide resolved
app/components/projects/settings/life_cycles/show_page_header_component.rb
Outdated
Show resolved
Hide resolved
app/components/projects/settings/life_cycles/show_page_header_component.rb
Outdated
Show resolved
Hide resolved
Thanks for the thorough review, @toy . It sparked quite some improvements I think. I fear this lead to additional code to review. I simply resolved all the conversations which I think to be addressed. Those where I am of a different opinion I left open and commented on. |
The flickering spec is addressed by #17412 |
...ponents/projects/settings/project_custom_field_sections/index_page_header_component.html.erb
Outdated
Show resolved
Hide resolved
...mponents/projects/settings/project_custom_field_sections/custom_field_row_component.html.erb
Show resolved
Hide resolved
app/components/projects/settings/life_cycles/step_component.html.erb
Outdated
Show resolved
Hide resolved
app/components/projects/settings/life_cycles/show_page_header_component.html.erb
Outdated
Show resolved
Hide resolved
I worked in or commented on your remarks @toy. Please take another look. |
Again, @toy, I would request a review from your side. |
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.
Looks good to me
definition = Project::LifeCycleStepDefinition.where(id: params[:definition_id]) | ||
definition = Project::LifeCycleStepDefinition.where(id: params[:id]) |
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.
Very much nitpick - value is still an array, so there may be a bit of confusion why relation is assigned to variable with singular name
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.
The variable name is correct in being singular since only a single element will ever be returned. So I find that appropriate. One could switch to using a find
and wrap that into an array explicitly but that I find too cumbersome.
@@ -639,9 +643,9 @@ | |||
|
|||
project_menu_items.each do |key, options| | |||
menu.push :"settings_#{key}", | |||
{ controller: "/projects/settings/#{key}", action: "show" }, | |||
{ controller: "/projects/settings/#{key}", action: "show" }.merge(options.slice(:action)), |
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.
{ controller: "/projects/settings/#{key}", action: "show" }.merge(options.slice(:action)), | |
{ controller: "/projects/settings/#{key}", action: "show", **options.slice(:action) }, |
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 find that harder to understand the the merge command.
@@ -2592,7 +2592,7 @@ en: | |||
label_none_parentheses: "(none)" | |||
label_not_contains: "doesn't contain" | |||
label_not_equals: "is not" | |||
label_life_cycle_plural: "Project lifecycle" | |||
label_life_cycle_step_plural: "Project lifecycle" |
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.
label_life_cycle_step_plural: "Project lifecycle" | |
label_life_cycle_steps: "Project lifecycle" |
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 changed that explicitly after noticing that a translation was no longer applied. I currently don't remember which component but there is a hard wired expectation that there is a label with a plural suffix. Otherwise I wouldn't even have put it into the way to nondescript label section.
Ticket
https://community.openproject.org/wp/58163
What are you trying to accomplish?
Out of scope from the original requirements as of now as it has not been implemented yet:
Screenshots
Changes of note
visit_tab!('backlogs')
. The menu however no longer uses tabs and adding all the helpers to that one page led to some cluttering in there.Merge checklist