Angular third party library components usage best practices advice requestAngular 2 (with CLI) and types - best practicesStrings Best Practice in Angular 2Angular 2 best practicesWhat is the best practice regarding routerLink and presentational components in Angular?Angular 3rd party library interactionAngular (2+) Component Structure and Design - best practicesBest practices for RxJS inside non-trivial Angular componentsHow to port an AngularJS UI component library to latest Angular?Angular 6 Library Components and SCSSAngular 6/7 circular dependency between libraries

Why does the Antonov AN-225 not have any winglets?

What is the minimum time required for final wash in film development?

Yet another hash table in C

A horrible Stockfish chess engine evaluation

Distinguish the explanations of Galadriel's test in LotR

GDPR rights when subject dies; does family inherit subject rights?

Intelligent Ants in the Amazon

What is a "Lear Processor" and how did it work?

What happens when adult Billy Batson says "Shazam"?

Having decision making power over someone's assets

Number of short hairs coming out of the base of the head Tefillin

Party going through airport security at separate times?

Can Jimmy hang on his rope?

Through: how to use it with subtraction of functions?

WTB Horizon 47c - small crack in the middle of the tire

The three greedy pirates

Does a wizard need their hands free in order to cause their familiar from the Find Familiar spell to reappear?

How do native German speakers usually express skepticism (using even) about a premise?

Is it OK to leave real names & info visible in business card portfolio?

How can a dictatorship government be beneficial to a dictator in a post-scarcity society?

Elf (adjective) vs. Elvish vs. Elven

Is there a strong legal guarantee that the U.S. can give to another country that it won't attack them?

Did the Ottoman empire suppress the printing press?

OR-backed serious games



Angular third party library components usage best practices advice request


Angular 2 (with CLI) and types - best practicesStrings Best Practice in Angular 2Angular 2 best practicesWhat is the best practice regarding routerLink and presentational components in Angular?Angular 3rd party library interactionAngular (2+) Component Structure and Design - best practicesBest practices for RxJS inside non-trivial Angular componentsHow to port an AngularJS UI component library to latest Angular?Angular 6 Library Components and SCSSAngular 6/7 circular dependency between libraries






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








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










share|improve this question




























    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










    share|improve this question
























      0












      0








      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










      share|improve this question














      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







      angular typescript angular7 ng-lightning






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Mar 26 at 0:50









      RalmsRalms

      271 silver badge7 bronze badges




      271 silver badge7 bronze badges






















          1 Answer
          1






          active

          oldest

          votes


















          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.






          share|improve this answer























          • Would there be another alternative? just wondering if there are other options to consider.

            – Ralms
            Mar 26 at 2: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 at 11:07










          Your Answer






          StackExchange.ifUsing("editor", function ()
          StackExchange.using("externalEditor", function ()
          StackExchange.using("snippets", function ()
          StackExchange.snippets.init();
          );
          );
          , "code-snippets");

          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "1"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader:
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          ,
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













          draft saved

          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55348367%2fangular-third-party-library-components-usage-best-practices-advice-request%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          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.






          share|improve this answer























          • Would there be another alternative? just wondering if there are other options to consider.

            – Ralms
            Mar 26 at 2: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 at 11:07















          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.






          share|improve this answer























          • Would there be another alternative? just wondering if there are other options to consider.

            – Ralms
            Mar 26 at 2: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 at 11:07













          0












          0








          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.






          share|improve this answer













          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.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Mar 26 at 1:36









          Joshua BrokawJoshua Brokaw

          414 bronze badges




          414 bronze badges












          • Would there be another alternative? just wondering if there are other options to consider.

            – Ralms
            Mar 26 at 2: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 at 11:07

















          • Would there be another alternative? just wondering if there are other options to consider.

            – Ralms
            Mar 26 at 2: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 at 11:07
















          Would there be another alternative? just wondering if there are other options to consider.

          – Ralms
          Mar 26 at 2:07





          Would there be another alternative? just wondering if there are other options to consider.

          – Ralms
          Mar 26 at 2: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 at 11: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 at 11:07








          Got a question that you can’t ask on public Stack Overflow? Learn more about sharing private information with Stack Overflow for Teams.







          Got a question that you can’t ask on public Stack Overflow? Learn more about sharing private information with Stack Overflow for Teams.



















          draft saved

          draft discarded
















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid


          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.

          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55348367%2fangular-third-party-library-components-usage-best-practices-advice-request%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Kamusi Yaliyomo Aina za kamusi | Muundo wa kamusi | Faida za kamusi | Dhima ya picha katika kamusi | Marejeo | Tazama pia | Viungo vya nje | UrambazajiKuhusu kamusiGo-SwahiliWiki-KamusiKamusi ya Kiswahili na Kiingerezakuihariri na kuongeza habari

          SQL error code 1064 with creating Laravel foreign keysForeign key constraints: When to use ON UPDATE and ON DELETEDropping column with foreign key Laravel error: General error: 1025 Error on renameLaravel SQL Can't create tableLaravel Migration foreign key errorLaravel php artisan migrate:refresh giving a syntax errorSQLSTATE[42S01]: Base table or view already exists or Base table or view already exists: 1050 Tableerror in migrating laravel file to xampp serverSyntax error or access violation: 1064:syntax to use near 'unsigned not null, modelName varchar(191) not null, title varchar(191) not nLaravel cannot create new table field in mysqlLaravel 5.7:Last migration creates table but is not registered in the migration table

          은진 송씨 목차 역사 본관 분파 인물 조선 왕실과의 인척 관계 집성촌 항렬자 인구 같이 보기 각주 둘러보기 메뉴은진 송씨세종실록 149권, 지리지 충청도 공주목 은진현