FlatfileButtonComponent may break during ngOnDestroy

[moreira]

Dsscription

When FlatfileButtonComponent's ngOnDestroy is called before ngOnInit, the flatfileImporter field isn't initialized throwing an error during the ngOnDestroy.

Notes

This issue can happen when a route change is triggered before the component is properly initialized. In this situation the ngOnInit isn't called but the ngOnDestroy is.

Screenshot

:

[sand-head]

I've found that it also throws an error if you let the component initialize, but a route change occurs before the button is clicked.

[kevin-induro]

I'm sure there's a nicer way to handle it than an empty catch block, but this is a huge issue for us. We're going to have to fork if this is not fixed because we regularly switch hide and show the button through an *ngIf.