[Design Pattern] Vendor Wrapper Pattern

The Vendor Wrapper Pattern is about isolating a third-party (vendor) library behind your own abstraction. Instead of scattering vendor-specific API calls throughout your app, you encapsulate them in a wrapper. This makes it easier to swap or update the vendor library later, and it keeps your codebase cleaner.

 

For example if you use ForntAwesome library, you might directly use it through your whole app, it seems to be easy, but when it comes to we need to support other icon library or custom icons then you need to find & replace code in you whole applciation which is not ideal.

 

The idea is never let 3rd party library directly be used inside your application. 

posted @   Zhentiw  阅读(2)  评论(0编辑  收藏  举报
相关博文:
阅读排行:
· 被坑几百块钱后,我竟然真的恢复了删除的微信聊天记录!
· 没有Manus邀请码?试试免邀请码的MGX或者开源的OpenManus吧
· 【自荐】一款简洁、开源的在线白板工具 Drawnix
· 园子的第一款AI主题卫衣上架——"HELLO! HOW CAN I ASSIST YOU TODAY
· Docker 太简单,K8s 太复杂?w7panel 让容器管理更轻松!
历史上的今天:
2021-03-03 [CSS 3] max()
2021-03-03 [Angular] Angular Asynchronous Form Validators
2021-03-03 [AWS] Serverless Kinesis and Dynamodb
2021-03-03 [AWS] Serverless Kinesis trigger Lambda and using ses to send email
2020-03-03 [Cypress] Combine Custom Cypress Commands into a Single Custom Command
2020-03-03 [Unit Testing Angular] RxJS Marble testing for Component
2017-03-03 [Ramda] R.project -- Select a Subset of Properties from a Collection of Objects in Ramda
点击右上角即可分享
微信分享提示