* FEATURE: add resume wizard popup
* code cleanup, copy edits
* FIX: address functionality, setting and copy issues
@fzngagan a few issues fixed
1. The resume button wasn't working (old reference to ``resumeDialog`` remained in callback.
2. This needs a wizard setting
3. It's not necessary to serialize the first step separately. We have all the steps in ``steps`` and steps have indexes.
4. Button copy
* Fix linting
* Ensure aa submission exists
* Apply prettier
Co-authored-by: angusmcleod <angus@mcleod.org.au>
* Add support button to admin-nav
* FIX: Security vulnerabilities with _blank anchor link
* Update pro support url
* UX: Create pro button custom styling
* UX: Merge support button focus styling with hover
* DEV: Move pro support url to setting
* UX: Change support button name to Pro Support
* DEV: Format stylesheet code
* DEV: Use variables and change selector specificity for pro button
* DEV: Hardcode pro-support url in button
* DEV: Remove support url localization
* DEV: Undo formatting fixes and add pro support button strings
* DEV: Undo formatting fixes auto applied
* DEV: Add space between selectors
* DEV: Convert scss variables to CSS Custom properties
* DEV: Fix linting
* FIX: Use SCSS variables for color manipulation functions
* DEV: Fix space before i18n
* DEV: Add new line at end of file
* DEV: Add new line at end of file
* DEV: Remove name attribute in localizations
* DEV: Remove padding from new line
* Add custom field improvements
This PR does a few things to improve our support of custom fields
1. Adds custom fields added by other plugins to the list in admin/wizards/custom-fields and the custom field list in the mapper selector
2. Adds support for json custom fields in the wizard actions
* Make eslint happy
* Make prettier happy
* Make rubocop happy
* Make ember template lint happy
* Don't assume we have the context in the selector
* Ensure custom fields don't require optional attributes (with tests)
* Re structure builder logic to allow for step conditionality
Concerns
- Performance. Look at whether the additional build in the steps controller can be reduced
- Does not work if applied to the last step.
- Certain conditions will not work with the first step(?)
- How should this be scoped to known functionality?
* Add indexes and conditions to steps and fields
* Complete and add spec
* Complete backend
* Complete step conditionality and field indexing
* Fix failing spec
* Update coverage
* Apply rubocop
* Apply prettier
* Apply prettier to wizard js
* Fix schema issues created in merge
* Remove setting label for force_final
* Improve client wizard cache naming
* Improve steps controller and spec conditionality
* Improve final step attribute naming
* Fix failing spec
* Linting
* Add one more final step test
* Linting
* Fix eslint issues
* Apply prettier
* Linting, syntax, merge and copy cleanups
* Update wizard-admin.scss
* Fix template linting
* Rubocop fixes
* FEATURE: added liquid based templating
* templating should be false by default
* added rspec tests for mapper templating
* wrapped templating tests in a context block
* added a custom liquid filter and tests
* ran rubocop on changed files
* DEV: minor variable and naming changes
* minor code formatting
* improved overall structure and tightened spec for custom filter
* added a spec template: false
* define method at the top of spec file
* naming convention
* removed extra space