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
Copy file name to clipboardexpand all lines: README.md
+1
Original file line number
Diff line number
Diff line change
@@ -17,6 +17,7 @@ Differences between the two APIs include a move away from a declarative system o
17
17
## Building and Running Open MCT Locally
18
18
19
19
Building and running Open MCT in your local dev environment is very easy. Be sure you have [Git](https://git-scm.com/downloads) and [Node.js](https://nodejs.org/) installed, then follow the directions below. Need additional information? Check out the [Getting Started](https://nasa.github.io/openmct/getting-started/) page on our website.
20
+
(These instructions assume you are installing as a non-root user; developers have [reported issues](https://github.com/nasa/openmct/issues/1151) running these steps with root privileges.)
Copy file name to clipboardexpand all lines: docs/src/design/proposals/APIRedesign_PeteRichards.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -99,7 +99,7 @@ To reduce interface depth, we can replace our own provider and registry patterns
99
99
100
100
## More angular: for all services
101
101
102
-
Increasing our commitment to angular would mean using more of the angular factorys, services, etc, and less of our home grown tools. We'd implement our services and extension points as angular providers, and make them configurable via app.config.
102
+
Increasing our commitment to angular would mean using more of the angular factories, services, etc, and less of our home grown tools. We'd implement our services and extension points as angular providers, and make them configurable via app.config.
103
103
104
104
As an example, registering a specific type of model provider in angular would look like:
0 commit comments