Wizard refactoring

[Hzaakk]

Description

Refactored all usage of wizard forms to remove duplicated code

Notes:

• all instances of the wizard form seemed to be the exact same, with the only exception being whether they include selectize or not (i decided to always include it). There was also one case where instead of "next step", the button said "submit" but i assumed it was a typo and included the normal template.

Fixes #654

Type of change

• New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Ensuring some forms still work properly (e.g. new project request which also has selectize functionality that should work still)

PR Self Evaluation

Strikethrough things that don’t make sense for your PR.

• My code follows the agreed upon best practices
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (if needed)
• My changes generate no new warnings
• Any dependent changes have been merged and published in the appropriate modules
• I have performed a self-review of my own code

[matthew-li]

Thanks for starting on this. Made some changes:

• Went with a slightly different approach: there is now a wizard_base.html that any template that is part of a wizard view should inherit from. This additionally removes the need to include this block in every single template:

  {% block head %}
  {{ wizard.form.media }}
  {% endblock %}
  

  • To include the form, use {{ block.super }} in the child template after the custom text for that template.
  • As part of this, dynamically rendered either a "Next Step" or a "Submit" button based on the step number.
• Added a selectize.html template that includes the CSS and JS for Selectize. The base wizard template does not include it--rather, only the child templates that need it should include it.
• Added a head block to base.html for custom CSS and JS.
• Moved request-related views into request subdirectories to make them easier to find.
• Removed some redundantly-defined paths in the views themselves by modifying how they are fetched in get_template_names.

@Hzaakk Can you review the changes and do some light testing (make sure the forms still render and submit properly)?