13ff801cc7
Using the [`geteventlisteners`](https://www.npmjs.com/package/geteventlisteners) package to allow capturing arbitrary event handlers specified as `@Output`s on any React-wrapper component. e.g.: ```html <fab-icon iconName="Add" (onClick)="handleIconClick($event)" (onMouseOver)="handleIconMouseOver($event)"></fab-icon> ``` ```typescript handleIconClick(ev: MouseEvent) { console.log('icon clicked!', ev); } handleIconMouseOver(ev: MouseEvent) { console.log('icon moused-over!', ev); } ``` Although extending global prototypes (i.e. not-yours) is bad practice, this is what Angular uses to capture events, and this seemed like the only way to get any arbitrary output from the element. The other option is to handle each specific event, which is a rather long list, and requires further maintenance, when the DOM, React or the component library adds events to listen to. This is similar in the idea as us passing any arbitrary attribute to the underlying React component. |
||
|---|---|---|
| .circleci | ||
| .vscode | ||
| apps | ||
| docs | ||
| libs | ||
| tools | ||
| .editorconfig | ||
| .gitignore | ||
| .prettierrc | ||
| CHANGELOG.md | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| README.md | ||
| angular.json | ||
| nx.json | ||
| package-lock.json | ||
| package.json | ||
| tsconfig.json | ||
| tsconfig.packages.json | ||
| tslint.json | ||
README.md
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/fabric | Documentation, quick start, and guides | Demo | Contributing | StackBlitz Template | Office UI 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)
Libraries
- core: Includes the Renderer and supporting logic to render Angular components with React implementations as React components.
- fabric: The light-weight Angular component wrappers that expose the Fabric React component api through common Angular components (including both imperative AND declrative syntax in many cases).
Roadmap
Initial work to prove the feasibility of adapting the Angular Renderer to output React managed components has concluded. We have moved beyond the initial simple Fabric components and expanded coverage to much of the available Office UI Fabric component library.
In the coming months we will continue to refine the component implementations as we use the angular-react core and fabric libraries in 2 real-world consumer facing production applications.
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.