* Remove this
* Update add user modal to show labels instead of icons
* Fill brand field on add device section
* add device form
* Save user device
* Binding form events from single function
* Add extra button Create User and Add Device
* Code style
* Create user and device form based on mockup
* Handling form validation
* Create User and Add another button
* Revert "Remove this"
This reverts commit 7102cf9b4a.
* Styled notification email
* Use single chosen field to select device model
* improvements
* Improve form validation message
* Delete unused template
* Code style improvements
* Fix typo on lodash flatMap statement
Device family as argument
* code style improvements
* Create function to render add user modal
* Handle error on user creation to prevent form buttons state
* Render users list without auto scroll when save and new btn is clicked
* Fix device data validation
* Add checkbox to create vmbox on user creation form
* Use waterfall flow for user creation
* Extract user create api call to new function
* Create vmbox only if requested
* Rename view data property to create vmbox
* Fix waterfall callbacks for user creation flow
* Add translations
* Refactor code and remove vmbox from callflow
* Do not show VMBox row field if there is none for user
* Do not create VMBox at usersSmartUpdateVMBox, if user has none
* Add gittatributes to use default line ending behavior
* Apply suggestions according to code review
* Code refactor according to review
* Move sub-module templates in their own `views` folder
By using `getTemplate()` we can specify which sub-module a template is
related to, enabling this behavior.
The templates names were shortened by stripping the name of their
sub-module from it since they are stored under their sub-module folder.
String templates are created using `getTemplate()` instead of
`monster.template()` that we are trying to depreciate.
* Only use `getTemplate()` for both regular and string templates