0

I'm a junior developer and I've been developing a Angular 7 web portal where I use many other components from some libraries such as ag grid or ng lightning.

As I'm starting to use the same component in many pages, my question is in regards to major version updates from those libraries that can have many breaking changes.

What is the best practice approach to require the less work when updating the libraries? Should I have my own reusable components that act as a wrapper the library respective component, so I only need to change the implementation in a single place? Or is there a better option?

Thank you very much in advance, Ralms

Ralms
  • 463
  • 5
  • 13

1 Answers1

0

It's kinda situational. If you're going to have multiple components that contain ag-grid or ng-lightning, then building a wrapper might make sense. If you're only using them once or twice and they don't share much commonality, it probably doesn't need a wrapper. Also, you can just choose to not take an update.

I'd suggest just leaving them as is, but if you reach a point where you think "it sure would be nice if all the xx-yyyyy components had a wrapper"... make it so.

Joshua Brokaw
  • 36
  • 4
  • Would there be another alternative? just wondering if there are other options to consider. – Ralms Mar 26 '19 at 02:07
  • It really depends how you're using the library components. If you can give some more specific detail, I can offer a more specific answer. But without that, I just point you to what I said before. It's situational. – Joshua Brokaw Mar 26 '19 at 11:07