Clone Reports

[eanders]

Merging this PR

• use the squash-merge strategy for PRs targeting a release-X branch

Description

• This exposes a New report from this universe button or link on HUD reports and the HMIS DQ Tool.
• Collects up Delete report and New report from this universe into an actions menu if both are present
• Centralizes action menu for reports

Type of change

• New feature

Checklist before requesting review

• I have performed a self-review of my code
• I have run the code that is being changed under ideal conditions, and it doesn't fail
• I have updated the documentation (or not applicable)
• I have added spec tests (or not applicable)
• I have provided testing instructions in this PR or the related issue (or not applicable)

[eanders]

@ttoomey and @dtgreiner if this looks like a good pattern for the action menu I'll add it to docs/code_patterns_and_conventions.md and we can begin pushing it out throughout the app.

[ttoomey]

looks good, thanks!

[ttoomey]

I think if we want this to become a pervasive pattern, it's worth it to wrap in a helper method. I think this has advantages over calling render directly:

• the params to the view are formalized (unlike render, which has no formal params)
• it's clear what partial is called (it's not relative to current controller)
• easier to swap out the rendering for something else that's more performant (a view component or content tags)
• more discoverable(?)
• could let us split the view in to 'action_menu' and 'action_button' to keep partials single-purpose and more maintainable

module ApplicationHelper
# ...
def action_menu_or_button(items:)
  return if items.empty?
  return render('/common/action_menu', items: items) if items.many?

  render('/common/action_button', item: items.sole) 
end

Suggested change

	= render 'common/action_menu_or_button', items: items
	= action_menu_or_button(items: items)