10dc637d72
The grpc-web generated library is loaded in the html page via a <script src="...">, and from the angular app's point of view, the proto variable is just an arbitrary external javascript handle. The envoy proxy host+port is controlled by environment.ts and environment.prod.ts. This may change if it proves problematic when integrating with envoy. The binary protos must be manually turned into human friendly strings, because js protos can not be dumped as JSONs. |
||
|---|---|---|
| .. | ||
| dist | ||
| e2e | ||
| src | ||
| .editorconfig | ||
| README.md | ||
| angular.json | ||
| karma.conf.js | ||
| package-lock.json | ||
| package.json | ||
| protractor.conf.js | ||
| tsconfig.json | ||
| tslint.json | ||
README.md
Channelzui
This project was generated with Angular CLI version 1.7.4.
Development server
Run ng serve for a dev server. Navigate to http://localhost:4200/. The app will automatically reload if you change any of the source files.
Code scaffolding
Run ng generate component component-name to generate a new component. You can also use ng generate directive|pipe|service|class|guard|interface|enum|module.
Build
Run ng build to build the project. The build artifacts will be stored in the dist/ directory. Use the -prod flag for a production build.
Running unit tests
Run ng test to execute the unit tests via Karma.
Running end-to-end tests
Run ng e2e to execute the end-to-end tests via Protractor.
Further help
To get more help on the Angular CLI use ng help or go check out the Angular CLI README.