Upgrade `office-ui-fabric-react` to latest version as of this PR.
Notice this is a **breaking change**:
* `office-ui-fabric-react` has deprecated some props - as usual - `@angular-react/fabric` doesn't support deprecated APIs and thus these were removed completely.
Expect a new minor version (0.6.0) in the release following this PR's merge, in accordance with semver.
* Updated to v0.5.1, Moved geteventlisteners module to local and revised JS to use es5 syntax, Minor typing fixes
* Updated changelog
* Remove changelog change
* Update @types/react
* Better type
* revert version bumps for core + fabric
* Upgrade react and react-dom to latest versions
* Updated Angular to v7.0, Updated office-ui-fabric-react to v6.110.0
* Fixed missing imports and reference errors
* Un-generic-ed EventListener (was causing errors since default EventListener is not generic)
* Removed noops on HoverCard and Tooltip component scss since they were moved to global styles in Fabric
* Upgrade office-ui-fabric-react to 6.110.0 + Add PlainCard and ExpandingCard components
* Renamed EventListener to IEventListener, Renamed some *.d.ts files to *.ts due to build issues
* Updated component property bindings to match new Fabric version
* Rename EventListener array and map to `I`-prefied versions to avoid confusion
- Package upgrades (non-breaking)
- Align repo to Prettier 1.15.3
- [includes] Revert decorators to their previous position in components, before the change in 1.14.
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.
* Fix bug in import.
* Add some margin below triangle.
* Updates to triangles to support user controlled size.
* Updates to the rendering style, showing content.
* Extra fix.
* Done updating performance profiles.
* Add dot-count to the triangles.
* Toggle profile images zoomed and not.
* Improve the layout a bit for fabric component docs.
* Fix format for output under buttons.
* Switching from Material to Semantic UI for demo.
There is already an Angular version for Material, so not much point of enabling Material React components in Angular.
* Add basic support for Semantic UI button.
* Update NX and add support for Angular Material.
* Added support for Angular Material and implemented simple nav.
Patterned after Angular-Material website.
* Update npm dependency.
* Fix bug when switching between perf pages.
* Rename Demo app to Docs
* Initial after adding demo app.
* Update demo app.
* Build docs for github hosting.
Shai Rose
Shai Rose
Jerry Wang
Ben Grynhaus
Nathan Walker
Ben Grynhaus
Ben Feely
Ben Feely
Ben Feely