Skip to content

Wrapper libraries

Jump to bottom
Ben Grynhaus edited this page Mar 19, 2019 · 2 revisions

While they don't contain much logic in regards to handling the DOM, rendering and internal interaction between React and Angular, they are the "glue" between a specific React UI library and Angular.

Currently we have two such wrapper libraries:

  1. @angular-react/fabric - wrapper library for office-ui-fabric-react
  2. @angular-react/semantic-ui - wrapper library for Semantic-UI-React

Philosophy

What separates Angular-React from other wrapper libraries, besides the fact that most solutions in this space are between AngularJS (aka Angular 1.x) and React is that we believe that application developers should focus on what they're already doing - writing Angular apps.

Other solutions create simple bindings between the two libraries/frameworks, on-demand, but avoid dealing with the caveats of merging two view libraries together, and require you to know both libraries well enough, and deal with concepts that may be foreign to you, as an Angular developer - like HOCs, render props etc as well as dealing with change detection.

What Angular-React aims to do is bridge the gap, such that the experience for the end developer of the app is one where they can keep thinking in "Angular" as much as possible, while still using other libraries under the hood.

Clone this wiki locally