You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This project welcomes contributions and suggestions. Most contributions require you to
4
+
agree to a Contributor License Agreement (CLA) declaring that you have the right to,
5
+
and actually do, grant us the rights to use your contribution. For details, visit
6
+
https://cla.microsoft.com.
7
+
8
+
When you submit a pull request, a CLA-bot will automatically determine whether you need
9
+
to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the
10
+
instructions provided by the bot. You will only need to do this once across all repositories using our CLA.
11
+
12
+
This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
13
+
For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/)
14
+
or contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments.
15
+
16
+
## Pull Requests Reviews
17
+
This is a simple guide to assist in reviewing Github pull requests locally within VS Code.
18
+
19
+
See: https://gist.github.com/piscisaureus/3342247
20
+
Locate the section for your github remote in the `.git/config` file. It looks like this:
21
+
22
+
```
23
+
[remote "origin"]
24
+
fetch = +refs/heads/*:refs/remotes/origin/*
25
+
url = git@github.com:joyent/node.git
26
+
```
27
+
28
+
Now add the line `fetch = +refs/pull/*/head:refs/remotes/origin/pr/*` to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:
Copy file name to clipboardExpand all lines: README.md
+14-69Lines changed: 14 additions & 69 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ Industry trends, organizational pressures, and other factors can lead to mandate
6
6
7
7
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.
@@ -18,7 +18,16 @@ Use of Angular-React allows consuming any React elements, but specifically Offic
18
18
- Use React component libraries with Angular
19
19
- Incrementally rewrite an Angular application into React (moving from atomic/leaf nodes upward into full features/pages until the entire app is re-written)
20
20
21
-
### Getting started
21
+
## Libraries
22
+
-[**core**][lib-core]: Includes the Renderer and supporting logic to render Angular components with React implementations as React components.
23
+
-[**fabric**][lib-fab]: 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).
24
+
25
+
# Roadmap
26
+
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][fab-c] component library.
27
+
28
+
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.
29
+
30
+
## Getting started
22
31
23
32
See our [Getting Started Guide][getting-started]
24
33
if you're building your first project with Angular-React.
@@ -30,70 +39,6 @@ You can look through the issues (which should be up-to-date on who is working on
This project welcomes contributions and suggestions. Most contributions require you to agree to a
37
-
Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us
38
-
the rights to use your contribution. For details, visit https://cla.microsoft.com.
39
-
40
-
When you submit a pull request, a CLA-bot will automatically determine whether you need to provide
41
-
a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions
42
-
provided by the bot. You will only need to do this once across all repos using our CLA.
43
-
44
-
This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
45
-
For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or
46
-
contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments.
47
-
48
-
### Pull Requests
49
-
See: https://gist.github.com/piscisaureus/3342247
50
-
Locate the section for your github remote in the `.git/config` file. It looks like this:
51
-
52
-
```
53
-
[remote "origin"]
54
-
fetch = +refs/heads/*:refs/remotes/origin/*
55
-
url = git@github.com:joyent/node.git
56
-
```
57
-
58
-
Now add the line `fetch = +refs/pull/*/head:refs/remotes/origin/pr/*` to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:
0 commit comments