@angular-react/fabric v0.1.7-alpha7-1

Office Fabric React support for Angular

Industry trends, organizational pressures, and other factors can lead to mandates regarding the use of component libraries or migration from one technology to another. In the case of Office UI Fabric, where its use is required, the client must be written in React (there is no Angular component library for the latest version). Rewrite from Angular to React may be cost-prohibitive or ill advised for other reasons.

Use of Angular-React allows consuming any React elements, but specifically Office UI Fabric, within an Angular 2+ application. The library of wrappers for Office UI Fabric simplifies the use of these components with Angular. However, any React code can make use of the custom Angular-React renderer.

Quick links

@angular-react/core | Documentation, quick start, and guides | Demo | Contributing | StackBlitz Template | Office Fabric

Typical Use Cases

• Use React component libraries with Angular
• Incrementally rewrite an Angular application into React (moving from atomic/leaf nodes upward into full features/pages until the entire app is re-written)

Getting started

See our Getting Started Guide if you're building your first project with Angular-React.

If you'd like to contribute, you must follow our contributing guidelines. You can look through the issues (which should be up-to-date on who is working on which features and which pieces are blocked) and make a comment.

High level stuff planned for Q2 2018 (April - June):

• Extend support for Fabric Buttons
• Extend support for Fabric Dialog
• Additional Fabric components TBD
• Table feature improvements
• Improve docs

Available Fabric features

In progress, planned, and non-planned Fabric features

The goal of Angular React

What do we mean by "high-quality"?

Browser and screen reader support