Feature/example

[mdtagg]

References issue #. Please review this @teammember1, @teamMember2.

Types of changes

• Bugfix (change which fixes an issue)
• New feature (change which adds functionality)
• Refactor (change which changes the codebase without affecting its external behavior)
• Non-breaking change (fix or feature that would cause existing functionality to work as expected)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Purpose

• application cards were being deleted through the use of a ref hook
• this was done to handle an event bubbling problem
• the delete button is inside of the card component so when delete was pressed the handle click inside of the card component was also called
• prior to this change there was an if block at the top level of the card onClick function that would check to see if the delete element that was clicked (which was being stored in the del ref) was in the del ref. If it was the onClick function on the card would exit and not run any code.
• This isnt ideal because there unneeded complexity being added to the app by way of the ref hook and unnecessary execution of functions.

-Also deleting all applications cards functionality was added

Approach

• I added an event.stopPropagation call in the delete handler to prevent the event from bubbling up to the parent.

• An extra parameter was added to the deleteApp function called in the application card.

• This action parameter takes either an empty string or "all" string.

• One extra line was added to the electron ipcMain "delete app" function that checks for an action.

• If "all" is true it deletes all the applications on the dashboard.

• This allows us to delete all example apps when we exit out of our example feature allowing a full seperation of concerns between main app functionality and our example feature

Learning