1591334400
Angular CLI: camelCase or kebab-case
Should Angular CLI options be in camel case or in kebab case?
Angular CLI supports options for commands. For example: ng build --prod
But, for these options should we use camelCase or kebab-case? Well, it turns out that the Angular CLI documentation is rather ambiguous about how you should write these command line options.
#javascript #angular #angular-cli #camel-case #js
1598940617
Angular is a TypeScript based framework that works in synchronization with HTML, CSS, and JavaScript. To work with angular, domain knowledge of these 3 is required.
In this article, you will get to know about the Angular Environment setup process. After reading this article, you will be able to install, setup, create, and launch your own application in Angular. So let’s start!!!
For Installing Angular on your Machine, there are 2 prerequisites:
First you need to have Node.js installed as Angular require current, active LTS or maintenance LTS version of Node.js
Download and Install Node.js version suitable for your machine’s operating system.
Angular, Angular CLI and Angular applications are dependent on npm packages. By installing Node.js, you have automatically installed the npm Package manager which will be the base for installing angular in your system. To check the presence of npm client and Angular version check of npm client, run this command:
· After executing the command, Angular CLI will get installed within some time. You can check it using the following command
Now as your Angular CLI is installed, you need to create a workspace to work upon your application. Methods for it are:
To create a workspace:
#angular tutorials #angular cli install #angular environment setup #angular version check #download angular #install angular #install angular cli
1591334400
Angular CLI: camelCase or kebab-case
Should Angular CLI options be in camel case or in kebab case?
Angular CLI supports options for commands. For example: ng build --prod
But, for these options should we use camelCase or kebab-case? Well, it turns out that the Angular CLI documentation is rather ambiguous about how you should write these command line options.
#javascript #angular #angular-cli #camel-case #js
1624138795
Learn How to use Angular Material Autocomplete Suggestions Search Input. I covered multiple use cases.
Please watch this video. I hope this video would be helpful for you to understand it and use it in your projects
Please subscribe: https://www.youtube.com/channel/UCL5nKCmpReJZZMe9_bYR89w
#angular #angular-material #angular-js #autocomplete #angular-material-autocomplete #angular-tutorial
1595337024
In Part 3 of this tutorial, we create the passenger info and flight search feature libraries. We use the generate project tool to create the mobile booking application and its test project. Finally, we create a mobile version of the flight search component template.
This tutorial is part of the Angular Architectural Patterns series.
In Part 2 of this tutorial, we used the generate project tool to generate the booking data access and shared data access workspace libraries with NgRx Store and Effects. We extracted a shared environments library and hooked everything up to the booking feature shell library.
In this part of the tutorial, we’re going to create the passenger info and flight search feature libraries, each with a routed component. After that, we’ll create the mobile booking application project and its end-to-end test project. Finally, we’ll use builder file replacement to create a mobile version of the flight search component template.
THIS AD MAKES CONTENT FREE. HIDE
Let’s create our first feature library, the passenger info feature which is part of the booking domain.
npm run generate-project -- library feature feature-passenger-info --scope=booking --npm-scope=nrwl-airlines
# or
yarn generate-project library feature feature-passenger-info --scope=booking --npm-scope=nrwl-airlines
<>
Generate passenger info feature library.
After generating the project using the previous commands and parameters, we get this file and folder structure.
libs/booking/feature-passenger-info
├── src
│ ├── lib
│ │ ├── passenger-info
│ │ │ ├── passenger-info.component.css
│ │ │ ├── passenger-info.component.html
│ │ │ ├── passenger-info.component.spec.ts
│ │ │ └── passenger-info.component.ts
│ │ ├── booking-feature-passenger-info.module.spec.ts
│ │ └── booking-feature-passenger-info.module.ts
│ ├── index.ts
│ └── test.ts
├── README.md
├── karma.conf.js
├── tsconfig.lib.json
├── tsconfig.spec.json
└── tslint.json
<>
The file and folder structure of the booking passenger info feature library.
This looks a little different from a feature shell library and a data access library.
After the generate project tool has created the workspace library with an entry point Angular module, it runs the commands in the next listing.
The generate project tool also removed the --no-common-module
flag from the ng generate module
command we saw earlier, since this Angular module will be declaring components.
ng generate component passenger-info --project=booking-feature-passenger-info --module=booking-feature-passenger-info.module.ts --display-block
<>
Generate component command run when generating a feature library.
Let’s look at the Angular module our tool has generated.
// booking-feature-passenger-info.module.ts
import { CommonModule } from '@angular/common';
import { NgModule } from '@angular/core';
import {
PassengerInfoComponent,
} from './passenger-info/passenger-info.component';
@NgModule({
declarations: [PassengerInfoComponent],
imports: [
CommonModule,
],
})
export class BookingFeaturePassengerInfoModule {}
<>
Initial entry point Angular module in the passenger info feature library.
The entry point Angular module shown in the previous listing is a good starting point. We need to set up the feature routing for our component though. This is done in the next listing.
// booking-feature-passenger-info.module.ts
import { CommonModule } from '@angular/common';
import { NgModule } from '@angular/core';
import { RouterModule, Routes } from '@angular/router';
import {
PassengerInfoComponent,
} from './passenger-info/passenger-info.component';
const routes: Routes = [
{
path: '',
pathMatch: 'full',
component: PassengerInfoComponent,
},
];
@NgModule({
declarations: [PassengerInfoComponent],
imports: [
RouterModule.forChild(routes),
CommonModule,
],
})
export class BookingFeaturePassengerInfoModule {}
<>
Passenger info feature Angular module with route configuration for its entry point component.
Nice! Now we’ve prepared our feature library to be hooked up to the feature shell library’s routing configuration.
The generated component is what you’d expect. What it’d display in a real booking application is not really important for the purpose of this article.
Let’s hook up this feature to the booking application’s routing by adding a route configuration to the booking feature shell Angular module as seen here.
#angular #angular-cli #angular-workspace #monorepo #nx #series-angular-architectural-patterns
1595333359
In the final part of this tutorial, we create the seatmap data access, seat listing feature, shared buttons UI, and shared formatting utilities library. Finally, we compare our approach with the full Nx toolchain.
This tutorial is part of the Angular Architectural Patterns series.
In Part 4 of this tutorial, we used our generate project tool to create the check-in data access library, the check-in feature shell library, the check-in desktop application, and the mobile check-in application. We hooked everything up and reviewed how much was automated by our tool.
In this part of the tutorial, we’re going to create the seatmap data access library with NgRx feature state. We then created the seat listing feature library and hooked it up to all applications with routing. Finally, we created the shared buttons UI library and the shared formatting utilities library which we used in the seat listing component.
THIS AD MAKES CONTENT FREE. HIDE
The shared seatmap feature has its own data access library. This is where we would add data services and application state management specific to the seatmap domain.
npm run generate-project -- library data-access --scope=seatmap --grouping-folder=shared/seatmap --npm-scope=nrwl-airlines --with-state
# or
yarn generate-project library data-access --scope=seatmap --grouping-folder=shared/seatmap --npm-scope=nrwl-airlines --with-state
<>
Generate the seatmap data access library.
For now, we’ll put the feature store and effects in place by using the --with-state
parameter of the generate project tool. Note that we use the nested grouping folder shared/seatmap
.
// seatmap-data-access.module.ts
import { NgModule } from '@angular/core';
import { EffectsModule } from '@ngrx/effects';
import { StoreModule } from '@ngrx/store';
import { SeatmapEffects } from './+state/seatmap.effects';
import * as fromSeatmap from './+state/seatmap.reducer';
@NgModule({
imports: [
StoreModule.forFeature(fromSeatmap.seatmapFeatureKey, fromSeatmap.reducer),
EffectsModule.forFeature([SeatmapEffects]),
],
})
export class SeatmapDataAccessModule {}
<>
The seatmap data access module.
The seatmap data access Angular module gives us an overview of what’s configured in the seatmap data access library. This is a good starting point.
ng run seatmap-data-access:lint
ng run seatmap-data-access:test --watch=false
<>
Lint and test the seatmap data access library.
Everything looks ready to go!
It’s time to add the first feature of the seatmap domain which is used in both the check-in and booking applications.
npm run generate-project -- library feature feature-seat-listing --scope=seatmap --grouping-folder=shared/seatmap --npm-scope=nrwl-airlines
# or
yarn generate-project library feature feature-seat-listing --scope=seatmap --grouping-folder=shared/seatmap --npm-scope=nrwl-airlines
<>
Generate the seatmap seat listing feature library.
Our tool generates an Angular module and a component for us.
To add this feature to our applications, we add a route to each feature shell module.
// check-in-feature-shell.module.ts
import { CommonModule } from '@angular/common';
import { NgModule } from '@angular/core';
import { RouterModule, Routes } from '@angular/router';
import { CheckInDataAccessModule } from '@nrwl-airlines/check-in/data-access';
import { SharedDataAccessModule } from '@nrwl-airlines/shared/data-access';
import { ShellComponent } from './shell/shell.component';
const routes: Routes = [
{
path: '',
component: ShellComponent,
children: [
{
path: '',
pathMatch: 'full',
redirectTo: 'seatmap', // 👈
},
{
path: 'seatmap', // 👈
loadChildren: () =>
import('@nrwl-airlines/seatmap/feature-seat-listing')
.then(esModule => esModule.SeatmapFeatureSeatListingModule),
},
],
},
];
@NgModule({
declarations: [ShellComponent],
exports: [RouterModule],
imports: [
RouterModule.forRoot(routes),
SharedDataAccessModule,
CheckInDataAccessModule,
CommonModule,
],
})
export class CheckInFeatureShellModule {}
#angular #angular-cli #angular-workspace #monorepo #nx #series-angular-architectural-patterns #ngrx