#Code maintainability

2 messages · Page 1 of 1 (latest)

dull barn
#

I've integrated ngx-datatable to an Angular app and I want to migrate a bunch of tables around the application to use this library. However, I'm thinking of first making a reusable component that wraps the library then use that component wherever. I'm trying to avoid having to modify various areas if the library has breaking changes or if I want to use a different table library.

Please what are your thoughts on this?

stone loom
#

More Component, more better, until too many Component then more sad. Only you could know when happy becomes sad 🙂