-
-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #33 from gjovanovicst/main
Update documentations and dependencies
- Loading branch information
Showing
16 changed files
with
1,713 additions
and
233 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,68 +1,29 @@ | ||
# Angular | ||
# AnywhereUI - Angular | ||
|
||
Angular has a pretty good story for integration with web components but there are a few issues with the developer experience. If you want to know what the story is without the bindings go here: https://stenciljs.com/docs/angular. | ||
|
||
With bindings the web components get wrapped in an Angular component and then immediately become available as Angular Components. Some of the advantages of doing this are that you get types for your components and you also get the ability to use ngmodel on inputs. Your developers then consuming your web components from Angular applications import an actual Angular Library and to them it feels as though they are interacting with Angular components. | ||
|
||
## Install | ||
|
||
```bash | ||
npm install @anywhere-ui/angular | ||
``` | ||
|
||
## Style | ||
|
||
The css dependencies should be added in `angular.json` file | ||
|
||
```json | ||
{ | ||
... | ||
|
||
"build": { | ||
... | ||
|
||
"options": { | ||
"styles": [ | ||
"./node_modules/@anywhere-ui/core/dist/anywhere-ui/anywhere-ui.css" | ||
], | ||
} | ||
}, | ||
... | ||
|
||
"test": { | ||
"styles": [ | ||
"./node_modules/@anywhere-ui/core/dist/anywhere-ui/anywhere-ui.css" | ||
], | ||
} | ||
## Build | ||
|
||
... | ||
Run: | ||
|
||
} | ||
```bash | ||
ng build anywhere-ui | ||
``` | ||
|
||
## Usage | ||
to build the project. The build artifacts will be stored in the `dist/` directory. | ||
|
||
```ts | ||
import { AnywhereUiModule } from '@anywhere-ui/angular'; | ||
## How to release a new version | ||
|
||
@NgModule({ | ||
... | ||
imports: [ | ||
AnywhereUiModule | ||
], | ||
... | ||
}) | ||
export class AppModule { } | ||
``` | ||
- Build the core package | ||
- Run build on this package | ||
- After building your library with `ng build anywhere-ui`, go to the dist folder `cd dist/anywhere-ui` and run `npm publish`. | ||
|
||
## Build | ||
## Running unit tests | ||
|
||
```bash | ||
ng build --configuration=production | ||
``` | ||
Run `ng test anywhere-ui` to execute the unit tests via [Karma](https://karma-runner.github.io). | ||
|
||
## How to release a new version | ||
## Further help | ||
|
||
- Build the core package | ||
- Run build on this package | ||
- Publish | ||
To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI Overview and Command Reference](https://angular.io/cli) page. |
Oops, something went wrong.