Migration: confirmation-modal component

[s223749059]

Description

Migrate the confirmation-modal component from CoffeeScript and Angular.js to TypeScript and Angular. The component is used at unit-tutorials-list component. It creates a confirmation dialog when users decide to delete a unit task. The action can be performed under aconvenor and aadmin account privileges.

How Has This Been Tested?

• First, log in as aconvenor or aadmin acount.
• Under the Administration section, select Units.
• After choosing a specific unit name, select the Tasks tab.
• In that, there is a list of unit tasks. Click on the red delete icon, it displays the confirmation dialog. Users can perform delete actions and receive alert messages on the top right hand side.

Before:

After:

• Successful delete a unit task:

• Error handling:

Testing Checklist:

• Tested in latest Chrome
• Tested in latest Safari
• Tested in latest Firefox

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings

[ublefo]

Tested locally and everything seems good. @satikaj Can you double check the code?

[maddernd]

The before and after image seem to have different formatting, it will need adjusting to look the same as the before image.

[s223749059]

The confirmation-model component GUI is updated regarding to the peer-review comments.

[ublefo]

Tested this locally and everything seems to be functioning correctly. No perceptible visual changes after the migration. Good work.

[aNebula]

Looks good to me.
Please recreate this Pull Request against the development branch of upstream repo doubtfire-lms/doubtfire-web. This is the final step for upstream merge.
You will likely face some conflicts in the src/app/doubtfire-angular.module.ts src/app/doubtfire-angularjs.module.ts files if you try to push the current changes. You could resolve those conflict then or you could potentially avoid conflict if you clone that repo first and copy across your particular changes and then raise a PR.