1576668444
Let’s create a very simple Angular form application that stores user information locally in memory on a server.
On submitting the form, we’ll populate the data on the next page and add two additional elements to display the guid and customer uid.
The Portfolio API - Grow your coding career effortlessly | gitconnected
First we’ll need Node & NPM installed.
To check if you have node installed run this command in your terminal:
node -v
To confirm that you have npm installed you can run this command:
**npm -v**
If not, you can download & install NodeJS & NPM from https://nodejs.org/en/
Install the Angular CLI:
npm install -g @angular/cli
Generate a new Angular project:
ng new charts6
Navigate to http://localhost:4200/. At this point the application will automatically reload if you change any of the source files. The initial page should be the default Angular 6 page:
The main Application component will have a UI Router that initially shows the Input User Data Form component. On submitting the form**, Application** component will show the Display User Data component.
Create components with ng cli
ng new angular-node-express
cd angular-node-express
ng generate component input-user-data-form --spec false
The CLI will create all the appropriate files and place them into the app folder
It should also add declarations into the app.module.ts
Next, we’ll add bootstrap 3 CSS library into the project to add styling.
npm install --save bootstrap@3
Afterwards add a path to “styles” array in the angular.json
"styles": [
"node_modules/bootstrap/dist/css/bootstrap.min.css",
"src/styles.css"
]
The Bootstrap grid system uses containers that hold rows and column. Rows and columns are percentage based. It is the container that changes responsively.
The container is used as a wrapper for the content.
We’ll choose a fluid container whose width will always be the width of the device.
<div class="container-fluid">
A grid row acts like a wrapper around the columns.
A row is created by adding the class row
to an element inside the container.
<div class="container-fluid">
<div class="row"></div>
</div>
Ideally, the number of columns equals 12 for every row. Different column class prefixes are used for different sized devices. Here 1 column takes up the size of 12 columns.
Change the app.component.html into the following:
<div class="container-fluid">
<div class="row">
<div class="col-xs-12">
<h1>Hello World!</h1>
</div>
</div>
</div>
Angular CLI uses webpack underneath to run the application on port 4200.
We’ll run our Node.js API endpoint on port 3000. But making an API call to another server (from port 4200) causes the CORS browser exception.
This is why we’ll use a proxy as a workround to the same-origin policy. The Proxy will re-route our API calls to a Node.js server to avoid the CORS exceptions. CORS is a browser security issue and does not apply to “backend to backend” communication.
All requests made to /api/...
from within our application will be forwarded to [http://localhost:3000/api/...](http://localhost:3000/api/....)
With the proxy, our application diagram will look like this:
Create the proxy.conf.json in root folder
{
"/api/*": {
"target": "http://localhost:3000",
"secure": false,
"logLevel": "debug",
"changeOrigin": true
}
}
When starting Angular & Proxy servers use the following command:
ng serve --proxy-config proxy.conf.json
First let’s focus on creating UI and work on API endpoints thereafter
There are 3 rules you must follow when making a Bootstrap form:
Set the input-user-data-form.component.html to the following:
input-user-data-form.component.html
<form>
<div class="form-group"> <!-- First Name -->
<label for="first_name" class="control-label">First Name</label>
<input type="text" class="form-control" id="first_name" name="first_name" placeholder="Martin">
</div>
<div class="form-group"> <!-- Last Name -->
<label for="last_name" class="control-label">Last Name</label>
<input type="text" class="form-control" id="last_name" name="last_name" placeholder="Toha">
</div>
<div class="form-group"> <!-- Email -->
<label for="email" class="control-label">E-mail</label>
<input type="text" class="form-control" id="email" name="email" placeholder="your@email.com">
</div>
<div class="form-group"> <!-- Zip Code-->
<label for="zipcode" class="control-label">Zip Code</label>
<input type="text" class="form-control" id="zipcode" name="zipcode" placeholder="#####">
</div>
<div class="form-group"> <!-- Password -->
<label for="password" class="control-label">Password</label>
<input type="text" class="form-control" id="password" name="password" placeholder="*****">
</div>
<div class="form-group"> <!-- Register Button -->
<button type="submit" class="btn btn-primary">Register</button>
</div>
</form>
Change selector in the input-user-data-form.component.ts to input-user-data-form
And add it to app.component.html
We are going to have to validate our fields prior to submitting the form to the backend. If a field is invalid, we can communicate it to the user by making the entire field red.
For each of the fields, we will:
Add the class .has-error
to the .form-group
div
And create a <p>
with the class .has-text
to explain the problem
input-user-data-form.component-validation.html
<form>
<div class="form-group has-error"> <!-- First Name -->
<label for="first_name" class="control-label">First Name</label>
<input type="text" class="form-control" id="first_name" name="first_name" placeholder="Martin">
<p id="first_name_error" class="help-block">Invalid first name.</p>
</div>
<div class="form-group has-error"> <!-- Last Name -->
<label for="last_name" class="control-label">Last Name</label>
<input type="text" class="form-control" id="last_name" name="last_name" placeholder="Toha">
<p id="last_name_error" class="help-block">Invalid last name.</p>
</div>
<div class="form-group has-error"> <!-- Email -->
<label for="email" class="control-label">E-mail</label>
<input type="text" class="form-control" id="email" name="email" placeholder="your@email.com">
<p id="email_error" class="help-block">Invalid email address.</p>
</div>
<div class="form-group has-error"> <!-- Zip Code -->
<label for="zipcode" class="control-label">Zip Code</label>
<input type="text" class="form-control" id="zipcode" name="zipcode" placeholder="#####">
<p id="zipcode_error" class="help-block">Invalid zip code.</p>
</div>
<div class="form-group has-error"> <!-- Password -->
<label for="password" class="control-label">Password</label>
<input type="text" class="form-control" id="password" name="password" placeholder="*****">
<p id="password_error" class="help-block">Invalid password.</p>
</div>
<div class="form-group has-error"> <!-- Register Button -->
<button type="submit" class="btn btn-primary">Register</button>
</div>
</form>
Here is the form with errors added for every field:
A reactive form is a bit different from template-driven forms by providing more predictability with synchronous access to the data model, immutability with observable operators, and change tracking through observable streams.
To use the reactive form, we must import the FormsModule & ReactiveFormsModule from the @angular/forms package and add it to our app.module.ts
Next, lets modify the input-user-data-form.component.
We’ll inject the formBuilder into the component for use in the ngOnInit life cycle method. FormBuilder a service that helps making forms easier.
The FormBuilder will create a FormGroup userForm with FormControls. Each FormControl has a default value and a set of Validators.
Think of the userForm as a schema for the actual values. It holds validation rules for fields inside the form.
We’ll add registered & submitted boolean flags to the Component. We’ll use these to indicate the current form state**.**
Also, we’ll create a validator function for every input, see invalidFirstName(), invalidLastName(), invalidEmail(), invalidZipcode(), invalidPassword().
A validator function will be used in markup to hide / show error messages for each field.
input-user-data-form.components.ts
import { Component, OnInit } from '@angular/core';
import { FormBuilder, FormGroup, FormControl, Validators } from '@angular/forms';
@Component({
selector: 'input-user-data-form',
templateUrl: './input-user-data-form.component.html',
styleUrls: ['./input-user-data-form.component.css']
})
export class InputUserDataFormComponent implements OnInit {
registered = false;
submitted = false;
userForm: FormGroup;
constructor(private formBuilder: FormBuilder)
{
}
invalidFirstName()
{
return (this.submitted && this.userForm.controls.first_name.errors != null);
}
invalidLastName()
{
return (this.submitted && this.userForm.controls.last_name.errors != null);
}
invalidEmail()
{
return (this.submitted && this.userForm.controls.email.errors != null);
}
invalidZipcode()
{
return (this.submitted && this.userForm.controls.zipcode.errors != null);
}
invalidPassword()
{
return (this.submitted && this.userForm.controls.password.errors != null);
}
ngOnInit()
{
this.userForm = this.formBuilder.group({
first_name: ['', Validators.required],
last_name: ['', Validators.required],
email: ['', [Validators.required, Validators.email]],
zipcode: ['', [Validators.required, Validators.pattern('^[0-9]{5}(?:-[0-9]{4})?$')]],
password: ['', [Validators.required, Validators.minLength(5), Validators.pattern('^(?=.*[a-z])(?=.*[A-Z])(?=.*[0-9])[a-zA-Z0-9]+$')]],
});
}
onSubmit()
{
this.submitted = true;
if(this.userForm.invalid == true)
{
return;
}
else
{
this.registered = true;
}
}
};
In the input-user-data-form.component.html, and for every Reactive form we’ll use a directive [formGroup]
to bind to userForm
variable we defined in the component
We’ll bind the onSubmit handler via the (ngSubmit)
directive.
To connect an HTML input element to a Reactive form we need to add formControlName
attribute to each of the form inputs.
We’ll use the *ngIf & [ngClass] directives to control error messages. The styles and validation markup will get displayed after user attempts to submit the form. This is controlled with [submitted]
property of the component.
After submitting the form, it will be validated every time user changes the input value, causing errors to show & hide dynamically.
input-user-data-form.component-02.html
<form [formGroup]="userForm" (ngSubmit)="onSubmit()">
<div class="form-group" [ngClass]="{ 'has-error': invalidFirstName() }"> <!-- First Name -->
<label for="first_name" class="control-label">First Name</label>
<input type="text" formControlName="first_name" class="form-control" id="first_name" name="first_name" placeholder="Martin">
<p *ngIf="invalidFirstName()" id="first_name_error" class="help-block">Invalid first name.</p>
</div>
<div class="form-group" [ngClass]="{ 'has-error': invalidLastName() }"> <!-- Last Name -->
<label for="last_name" class="control-label">Last Name</label>
<input type="text" formControlName="last_name" class="form-control" id="last_name" name="last_name" placeholder="Toha">
<p *ngIf="invalidLastName()" id="last_name_error" class="help-block">Invalid last name.</p>
</div>
<div class="form-group" [ngClass]="{ 'has-error': invalidEmail() }"> <!-- Email -->
<label for="email" class="control-label">E-mail</label>
<input type="text" formControlName="email" class="form-control" id="email" name="email" placeholder="your@email.com">
<p *ngIf="invalidEmail()" id="email_error" class="help-block">Invalid email address.</p>
</div>
<div class="form-group" [ngClass]="{ 'has-error': invalidZipcode() }"> <!-- Zip Code-->
<label for="zipcode" class="control-label">Zip Code</label>
<input type="text" formControlName="zipcode" class="form-control" id="zipcode" name="zipcode" placeholder="#####">
<p *ngIf="invalidZipcode()" id="zipcode_error" class="help-block">Invalid zip code.</p>
</div>
<div class="form-group" [ngClass]="{ 'has-error': invalidPassword() }"> <!-- Password -->
<label for="password" class="control-label">Password</label>
<input type="password" formControlName="password" class="form-control" id="password" name="password" placeholder="*****">
<p *ngIf="invalidPassword()" id="password_error" class="help-block">Invalid password.</p>
</div>
<div class="form-group has-error"> <!-- Register Button -->
<button type="submit" class="btn btn-primary">Register</button>
</div>
</form>
Here is what the form looks like initially:
And the form after filling out some fields with error:
Looks good so far! Lets continue with the next component.
The next Angular component will display user data. This will be a simple component that visualizes a data model passed into it.
Lets create a data model UserInfoModel in app/models, we’ll make it deserialize an object when its passed into the constructor.
export class UserInfoModel
{
guid: string;
customerUid: string;
first_name: string;
last_name: string;
email: string;
zipcode: string;
password: string;
constructor(obj: any = null)
{
if(obj != null)
{
Object.assign(this, obj);
}
}
}
The view display-user-data.component.html binds to the model via interpolation {{…}} and displays the information.
display-user-data.component.html
<legend>User Information</legend>
<div>
<div class="form-group row"> <!-- GUD -->
<label class="col-xs-6 col-form-label">GUID</label>
<div class="col-xs-6">{{user.guid}}</div>
</div>
<div class="form-group row"> <!-- Customer UID -->
<label class="col-xs-6 col-form-label">Customer UID</label>
<div class="col-xs-6">{{user.customerUid}}</div>
</div>
<div class="form-group row"> <!-- First Name -->
<label class="col-xs-6 col-form-label">First Name</label>
<div class="col-xs-6">{{user.first_name}}</div>
</div>
<div class="form-group row"> <!-- Last Name -->
<label class="col-xs-6 col-form-label">Last Name</label>
<div class="col-xs-6">{{user.last_name}}</div>
</div>
<div class="form-group row"> <!-- E-mail -->
<label class="col-xs-6 col-form-label">E-mail</label>
<div class="col-xs-6">{{user.email}}</div>
</div>
<div class="form-group row"> <!-- Zip Code -->
<label class="col-xs-6 col-form-label">Zip Code</label>
<div class="col-xs-6">{{user.zipcode}}</div>
</div>
<div class="form-group row"> <!-- Password -->
<label class="col-xs-6 col-form-label">Password</label>
<div class="col-xs-6">{{user.password}}</div>
</div>
</div>
And just for testing purposes, DisplayUserDataComponent class will assign some default values into the UserInfoModel
display-user-data.component.ts
import { Component, OnInit } from '@angular/core';
import {UserInfoModel} from '../models/userInfo'
@Component({
selector: 'display-user-data',
templateUrl: './display-user-data.component.html',
styleUrls: ['./display-user-data.component.css']
})
export class DisplayUserDataComponent implements OnInit {
user: UserInfoModel = new UserInfoModel({guid: "D21ds12x",
customerUid: "cust2dsa12dsa",
first_name: "John",
last_name: "Doe",
email: "email@email.com",
zipcode: 10283,
password: "Idasn2x2#"});
constructor() { }
ngOnInit()
{
}
}
Both of the pages look great!
Now, lets connect the Router into the AppComponent to establish a page flow
Our goal with routing is to have the InputUserDataFormComponent
rendered when the url is /
, and DisplayUserDataComponent
shown when the url is /user/:uid
First, lets setup the imports to @angular/router, then define an array routes of our paths and destination pages.
const routes: Routes = [
{
path: '',
component: InputUserDataFormComponent
},
{
path: 'user/:uid',
component: DisplayUserDataComponent
}
];
In the imports
add RouterModule.forRoot(routes)
import { BrowserModule } from '@angular/platform-browser';
import { NgModule } from '@angular/core';
import { ReactiveFormsModule, FormsModule } from '@angular/forms';
import { AppComponent } from './app.component';
import { InputUserDataFormComponent } from './input-user-data-form/input-user-data-form.component';
import { DisplayUserDataComponent } from './display-user-data/display-user-data.component';
import { Routes, RouterModule } from "@angular/router";
const routes: Routes = [
{
path: '',
component: InputUserDataFormComponent
},
{
path: 'user/:uid',
component: DisplayUserDataComponent
}
];
@NgModule({
declarations: [
AppComponent,
InputUserDataFormComponent,
DisplayUserDataComponent
],
imports: [
BrowserModule,
FormsModule,
ReactiveFormsModule,
RouterModule.forRoot(routes)
],
providers: [],
bootstrap: [AppComponent]
})
export class AppModule { }
Place the router-outlet
in the app.component.html
<div class="container-fluid">
<div class="row">
<div class="col-xs-12">
<router-outlet></router-outlet>
</div>
</div>
</div>
Now the initial “/” root page looks like this:
Type “/user/a01” in the address bar and you get the User Information page
All works as intended on the client! Now lets continue with creation of API endpoint.
We’ll use the express-generator-api to make a Node.js API quickly by generating a project.
Install express-generator:
npm install -g express-generator-api
Create the API:
express-api angular-node-express-api & cd angular-node-express-api
Install dependencies:
npm install
Тhe file structure generated should be the following:
At this point all the basics of an API have been implemented by the generator.
For example, body parser & cookie parser are part of the app.js. Here express will try identify any JSON data that comes into our application and parse it for us.
Next, we are going to make the following API endpoints.
/customer
will insert a new customer and return auto-incremented customer.id
/customer/:uid
will retrieve a single customer by customer uid
/generate_guid
will generate a tracking_guide that Angular UI will use when creating a new customer
Lets copy users.js to generate_uid.js just to have a basic router. We’ll modify this router to return a random uid
Install uid-safe, which generates a uid safe for cookies
npm install uid-safe
Include it in generate_uid.js
var uid = require('uid-safe')
And return it with the response
var express = require('express');
var uid = require('uid-safe');
var router = express.Router();
/* GET a guid. */
router.get('/', function(req, res, next)
{
var strUid = uid.sync(18);
res.json({guid: strUid});
});
module.exports = router;
We’ll need to hook up the generate_uid router in the app.js
app.use('/api/v1/generate_uid', generate_uid);
The route returns a JSON with the GUID. Great!
{"guid":"K7VPC3I9kxIJ4Ct2_2ZR7Xb1"}
For every API service I usually have a model for the data and a service that performs all CRUD operations with it; that way there is a level of abstraction between the API request, storage & validation, but also a good way to access the service from anywhere in the application.
In this example, we’ll simply store customer data in memory.
The service will increment a customer UID every time a new customer is created.
We’ll use that customer UID to retrieve the customer data as well.
Create the models directory and add the following model.customer.js in there.
class CustomerModel
{
constructor(uid, first_name, last_name, email, zipcode, password)
{
this.uid = uid;
this.first_name = first_name;
this.last_name = last_name;
this.email = email;
this.zipcode = zipcode;
this.password = password;
}
}
module.exports = CustomerModel;
Then, create services directory and add a service.customer.js in there.
CustomerService implements all the CRUD operations create, read, update and delete the CustomerModel. It uses the counter to increment the customer uid; and stores all the customers into the customers object.
It’s important to validate our data on the server as well as the client. I usually keep validation as part of the service object, which is either a separate method or part of the CRUD operation.
We’ll implement the validation using the fastest-validator library.
Install fastest-validator library:
npm install fastest-validator --save
Import it in the CustomerService service object and create an instance of the Validator with custom schema.
var validator = require('fastest-validator');
The Schema object contains all validation rules, which is then used by the Validator instance to validate data against it.
Then, we’ll need to notify UI if validation fails on the server. If that happens, the create operation will throw an Error with list of errors for every failed validation.
services\service.customer.js
The list of errors will propagate into the response, which will be handled by Angular to communicate an error.
const CustomerModel = require("../models/model.customer");
let Validator = require('fastest-validator');
let customers = {};
let counter = 0;
/* create an instance of the validator */
let customerValidator = new Validator();
/* use the same patterns as on the client to validate the request */
let namePattern = /([A-Za-z\-\’])*/;
let zipCodePattern = /^[0-9]{5}(?:-[0-9]{4})?$/;
let passwordPattern = /^(?=.*[a-z])(?=.*[A-Z])(?=.*[0-9])[a-zA-Z0-9]+$/;
/* customer validator shema */
const customerVSchema = {
guid: {type: "string", min: 3},
first_name: { type: "string", min: 1, max: 50, pattern: namePattern},
last_name: { type: "string", min: 1, max: 50, pattern: namePattern},
email: { type: "email", max: 75 },
zipcode: { type: "string", max: 5, pattern: zipCodePattern},
password: { type: "string", min: 2, max: 50, pattern: passwordPattern}
};
/* static customer service class */
class CustomerService
{
static create(data)
{
var vres = customerValidator.validate(data, customerVSchema);
/* validation failed */
if(!(vres === true))
{
let errors = {}, item;
for(const index in vres)
{
item = vres[index];
errors[item.field] = item.message;
}
throw {
name: "ValidationError",
message: errors
};
}
let customer = new CustomerModel(data.first_name, data.last_name, data.email, data.zipcode, data.password);
customer.uid = 'c' + counter++;
customers[customer.uid] = customer;
return customer;
}
static retrieve(uid)
{
if(customers[uid] != null)
{
return customers[uid];
}
else
{
throw new Error('Unable to retrieve a customer by (uid:'+ uid +')');
}
}
static update(uid, data)
{
if(customers[uid] != null)
{
const customer = customers[uid];
Object.assign(customer, data);
}
else
{
throw new Error('Unable to retrieve a customer by (uid:'+ cuid +')');
}
}
static delete(uid)
{
if(customers[uid] != null)
{
delete customers[uid];
}
else
{
throw new Error('Unable to retrieve a customer by (uid:'+ cuid +')');
}
}
}
module.exports = CustomerService;
Lets connect the CustomerService to express router.
We’ll be using the async / await, which is a better way to write asynchronous code. Previous options are callbacks and promises, in fact async/await is built on top of promises; but async / await make the code behave & read a little more like synchronous code.
In the following router we implement all the CRUD operations using the CustomerService singleton.
Take a look at the create operation, where we submit user data and how errors are propagated into the response via try / catch block. The code is easy to read.
var express = require('express');
var router = express.Router();
var CustomerService = require('../services/service.customer');
/* GET customer listing. */
router.get('/', async function(req, res, next)
{
res.json({error: "Invalid Customer UID."});
});
/* adds a new customer to the list */
router.post('/', async (req, res, next) =>
{
const body = req.body;
try
{
const customer = await CustomerService.create(body);
if(body.guid != null)
{
customer.guid = body.guid;
}
res.cookie('guid', customer.guid, { maxAge: 900000, httpOnly: true });
// created the customer!
return res.status(201).json({ customer: customer });
}
catch(err)
{
if (err.name === 'ValidationError')
{
return res.status(400).json({ error: err.message });
}
// unexpected error
return next(err);
}
});
/* retrieves a customer by uid */
router.get('/:id', async (req, res, next) =>
{
try
{
const customer = await CustomerService.retrieve(req.params.id);
return res.json({ customer: customer });
}
catch(err)
{
// unexpected error
return next(err);
}
});
/* updates the customer by uid */
router.put('/:id', async (req, res, next) =>
{
try
{
const customer = await CustomerService.update(req.params.id, req.body);
return res.json({ customer: customer });
}
catch(err)
{
// unexpected error
return next(err);
}
});
/* removes the customer from the customer list by uid */
router.delete('/:id', async (req, res, next) =>
{
try
{
const customer = await CustomerService.delete(req.params.id);
return res.json({success: true});
}
catch(err)
{
// unexpected error
return next(err);
}
});
module.exports = router;
Next, we’ll need to modify the input-user-data-form.component & its template to support showing the server side errors, in case the validation fails on the server.
In the InputUserDataFormComponent we’ll add the serviceErrors object, which will contain all the server side errors for each fields. And add to the validator methods to check if the error message for that field exists, like so:
app\input-user-data-form.component.ts
We’ll also modify the onSubmit method, and add an error handler to our request which will simply set serviceErrors object.
app\input-user-data-form\input-user-data-form.component.ts
Next we’ll add a reference to server side errors in the input-user-data-form.component.html template to display a server side error in case it exists:
app\input-user-data-form\input-user-data-form.component.html
Now, we’ll know if validation fails on the server, since messages are going to be propagated to Angular UI.
Everything looks good, lets connect our routers in the app.js
var express = require('express');
var path = require('path');
var cookieParser = require('cookie-parser');
var bodyParser = require('body-parser');
var generate_uid = require('./routes/generate_uid');
var customer = require('./routes/customer');
var app = express();
app.use(bodyParser.json());
app.use(bodyParser.urlencoded({ extended: false }));
app.use(cookieParser())
app.use('/api/v1/customer', customer);
app.use('/api/v1/generate_uid', generate_uid);
module.exports = app;
We are done creating the application, now a couple of minor details.
We are using a proxy in order to go around the CORS browser issue by having the Webpack on port 4200 communicate with Node.js server on port 3000. This is a good solution for the development environment, but we’ll need to have a better implementation when moving to production.
The API server will need to either enable the API for all origins or white list our access point.
To enable our API for all is easy, just add the following code to app.js
app.use(function(req, res, next) {
res.header("Access-Control-Allow-Origin", "*");
res.header("Access-Control-Allow-Headers", "Origin, X-Requested-With, Content-Type, Accept");
next();
});
Another minor detail we haven’t covered is handling of Uncaught Exceptions
Because Node.js runs on a single processor uncaught exceptions are an issue to be aware of when developing applications.
When your application throws an uncaught exception you should consider that your application is now running in an unclean state. You can’t reliably continue your program at this point because you don’t really know what got affected by the error.
The best way to handle a crash is to collect as much data about it, send the errors to an external crash service or log it; and restart the server.
For our simple application, we’ll implement the appropriate functions, just place these in the beginning of your app.js
I’ll keep the reporter method empty, which we will connect in a later article to an external crash service
let reporter = function (type, ...rest)
{
// remote reporter logic goes here
};
/* handle an uncaught exception & exit the process */
process.on('uncaughtException', function (err)
{
console.error((new Date).toUTCString() + ' uncaughtException:', err.message);
console.error(err.stack);
reporter("uncaughtException", (new Date).toUTCString(), err.message, err.stack);
process.exit(1);
});
/* handle an unhandled promise rejection */
process.on('unhandledRejection', function (reason, promise)
{
console.error('unhandled rejection:', reason.message || reason);
reporter("uncaughtException", (new Date).toUTCString(), reason.message || reason);
})
Finally! To start the API server:
npm start
Try hitting the http://localhost:3000/api/v1/generate_uid
or http://localhost:3000/api/v1/customer
And you should see some JSON data.
To quickly integrate the Angular application we are going to:
Import & Inject HttpClient & Router into the InputUserDataFormComponent
Next, we’ll retrieve the GUID from the ‘/api/v1/generate_uid’ API service in the constructor of the InputUserDataFormComponent and set the guid variable
constructor of InputUserDataFormComponent
In the onSubmit method of the InputUserDataFormComponent we’ll post the data into the ‘/api/v1/customer’ service & navigate the Angular Router to the next page /user/:id
The full source code:
input-user-data-form.component-wroute-api.ts
import { Component, OnInit } from '@angular/core';
import { FormBuilder, FormGroup, FormControl, Validators } from '@angular/forms';
import { HttpClient } from "@angular/common/http";
import { Router } from "@angular/router";
@Component({
selector: 'input-user-data-form',
templateUrl: './input-user-data-form.component.html',
styleUrls: ['./input-user-data-form.component.css']
})
export class InputUserDataFormComponent implements OnInit {
registered = false;
submitted = false;
userForm: FormGroup;
guid: string;
serviceErrors:any = {};
constructor(private formBuilder: FormBuilder, private http: HttpClient, private router: Router)
{
this.http.get('/api/v1/generate_uid').subscribe((data:any) => {
this.guid = data.guid;
}, error => {
console.log("There was an error generating the proper GUID on the server", error);
});
}
invalidFirstName()
{
return (this.submitted && (this.serviceErrors.first_name != null || this.userForm.controls.first_name.errors != null));
}
invalidLastName()
{
return (this.submitted && (this.serviceErrors.last_name != null || this.userForm.controls.last_name.errors != null));
}
invalidEmail()
{
return (this.submitted && (this.serviceErrors.email != null || this.userForm.controls.email.errors != null));
}
invalidZipcode()
{
return (this.submitted && (this.serviceErrors.zipcode != null || this.userForm.controls.zipcode.errors != null));
}
invalidPassword()
{
return (this.submitted && (this.serviceErrors.password != null || this.userForm.controls.password.errors != null));
}
ngOnInit()
{
this.userForm = this.formBuilder.group({
first_name: ['', [Validators.required, Validators.maxLength(50)]],
last_name: ['', [Validators.required, Validators.maxLength(50)]],
email: ['', [Validators.required, Validators.email, Validators.maxLength(75)]],
zipcode: ['', [Validators.required, Validators.pattern('^[0-9]{5}(?:-[0-9]{4})?$')]],
password: ['', [Validators.required, Validators.minLength(5), Validators.pattern('^(?=.*[a-z])(?=.*[A-Z])(?=.*[0-9])[a-zA-Z0-9]+$')]],
});
}
onSubmit()
{
this.submitted = true;
if(this.userForm.invalid == true)
{
return;
}
else
{
let data: any = Object.assign({guid: this.guid}, this.userForm.value);
this.http.post('/api/v1/customer', data).subscribe((data:any) => {
let path = '/user/' + data.customer.uid;
this.router.navigate([path]);
}, error =>
{
this.serviceErrors = error.error.error;
});
this.registered = true;
}
}
};
Then lets Import & Inject HttpClient & ActivatedRoute into the DisplayUserDataComponent
Retrieve customer data from the ‘/api/v1/customer/:id’ API and populate the UserInfoModel with new data, and have DisplayUserDataComponent view redraw itself with new data via interpolation {{…}}
display-user-data.component-wroute-api.ts
import { Component, OnInit } from '@angular/core';
import {UserInfoModel} from '../models/userInfo';
import { HttpClient } from "@angular/common/http";
import { ActivatedRoute } from '@angular/router';
@Component({
selector: 'display-user-data',
templateUrl: './display-user-data.component.html',
styleUrls: ['./display-user-data.component.css']
})
export class DisplayUserDataComponent implements OnInit
{
user: UserInfoModel = new UserInfoModel({guid: "D21ds12x",
uid: "cust2dsa12dsa",
first_name: "John",
last_name: "Doe",
email: "email@email.com",
zipcode: 10283,
password: "Idasn2x2#"});
constructor(private http: HttpClient, private route: ActivatedRoute) {
}
private subscriber: any;
ngOnInit()
{
this.subscriber = this.route.params.subscribe(params => {
this.http.get('/api/v1/customer/' + params.uid).subscribe((data:any) => {
this.user = new UserInfoModel(data.customer);
});
});
}
}
The initial page of the application ‘/’:
Fill in the form and press Register:
Next page, the user information is displayed.
After creating a customer, you can also type in the customer url followed by customer uid to retrieve customer data:
http://localhost:3000/api/v1/customer/c0
{"customer":{"first_name":"John","last_name":"Doe","email":"john.doe@gmail.com","zipcode":"12345","password":"Udsakln12dsa","uid":"c0","guid":"gCnqJdp3saMNPpJfXPj6DORy"}}
Angular UI:
https://github.com/jsmuster/angular-node-express
Node.js + Express API:
https://github.com/jsmuster/angular-node-express-api
#nodejs #angular #javascript #node-js
1576668444
Let’s create a very simple Angular form application that stores user information locally in memory on a server.
On submitting the form, we’ll populate the data on the next page and add two additional elements to display the guid and customer uid.
The Portfolio API - Grow your coding career effortlessly | gitconnected
First we’ll need Node & NPM installed.
To check if you have node installed run this command in your terminal:
node -v
To confirm that you have npm installed you can run this command:
**npm -v**
If not, you can download & install NodeJS & NPM from https://nodejs.org/en/
Install the Angular CLI:
npm install -g @angular/cli
Generate a new Angular project:
ng new charts6
Navigate to http://localhost:4200/. At this point the application will automatically reload if you change any of the source files. The initial page should be the default Angular 6 page:
The main Application component will have a UI Router that initially shows the Input User Data Form component. On submitting the form**, Application** component will show the Display User Data component.
Create components with ng cli
ng new angular-node-express
cd angular-node-express
ng generate component input-user-data-form --spec false
The CLI will create all the appropriate files and place them into the app folder
It should also add declarations into the app.module.ts
Next, we’ll add bootstrap 3 CSS library into the project to add styling.
npm install --save bootstrap@3
Afterwards add a path to “styles” array in the angular.json
"styles": [
"node_modules/bootstrap/dist/css/bootstrap.min.css",
"src/styles.css"
]
The Bootstrap grid system uses containers that hold rows and column. Rows and columns are percentage based. It is the container that changes responsively.
The container is used as a wrapper for the content.
We’ll choose a fluid container whose width will always be the width of the device.
<div class="container-fluid">
A grid row acts like a wrapper around the columns.
A row is created by adding the class row
to an element inside the container.
<div class="container-fluid">
<div class="row"></div>
</div>
Ideally, the number of columns equals 12 for every row. Different column class prefixes are used for different sized devices. Here 1 column takes up the size of 12 columns.
Change the app.component.html into the following:
<div class="container-fluid">
<div class="row">
<div class="col-xs-12">
<h1>Hello World!</h1>
</div>
</div>
</div>
Angular CLI uses webpack underneath to run the application on port 4200.
We’ll run our Node.js API endpoint on port 3000. But making an API call to another server (from port 4200) causes the CORS browser exception.
This is why we’ll use a proxy as a workround to the same-origin policy. The Proxy will re-route our API calls to a Node.js server to avoid the CORS exceptions. CORS is a browser security issue and does not apply to “backend to backend” communication.
All requests made to /api/...
from within our application will be forwarded to [http://localhost:3000/api/...](http://localhost:3000/api/....)
With the proxy, our application diagram will look like this:
Create the proxy.conf.json in root folder
{
"/api/*": {
"target": "http://localhost:3000",
"secure": false,
"logLevel": "debug",
"changeOrigin": true
}
}
When starting Angular & Proxy servers use the following command:
ng serve --proxy-config proxy.conf.json
First let’s focus on creating UI and work on API endpoints thereafter
There are 3 rules you must follow when making a Bootstrap form:
Set the input-user-data-form.component.html to the following:
input-user-data-form.component.html
<form>
<div class="form-group"> <!-- First Name -->
<label for="first_name" class="control-label">First Name</label>
<input type="text" class="form-control" id="first_name" name="first_name" placeholder="Martin">
</div>
<div class="form-group"> <!-- Last Name -->
<label for="last_name" class="control-label">Last Name</label>
<input type="text" class="form-control" id="last_name" name="last_name" placeholder="Toha">
</div>
<div class="form-group"> <!-- Email -->
<label for="email" class="control-label">E-mail</label>
<input type="text" class="form-control" id="email" name="email" placeholder="your@email.com">
</div>
<div class="form-group"> <!-- Zip Code-->
<label for="zipcode" class="control-label">Zip Code</label>
<input type="text" class="form-control" id="zipcode" name="zipcode" placeholder="#####">
</div>
<div class="form-group"> <!-- Password -->
<label for="password" class="control-label">Password</label>
<input type="text" class="form-control" id="password" name="password" placeholder="*****">
</div>
<div class="form-group"> <!-- Register Button -->
<button type="submit" class="btn btn-primary">Register</button>
</div>
</form>
Change selector in the input-user-data-form.component.ts to input-user-data-form
And add it to app.component.html
We are going to have to validate our fields prior to submitting the form to the backend. If a field is invalid, we can communicate it to the user by making the entire field red.
For each of the fields, we will:
Add the class .has-error
to the .form-group
div
And create a <p>
with the class .has-text
to explain the problem
input-user-data-form.component-validation.html
<form>
<div class="form-group has-error"> <!-- First Name -->
<label for="first_name" class="control-label">First Name</label>
<input type="text" class="form-control" id="first_name" name="first_name" placeholder="Martin">
<p id="first_name_error" class="help-block">Invalid first name.</p>
</div>
<div class="form-group has-error"> <!-- Last Name -->
<label for="last_name" class="control-label">Last Name</label>
<input type="text" class="form-control" id="last_name" name="last_name" placeholder="Toha">
<p id="last_name_error" class="help-block">Invalid last name.</p>
</div>
<div class="form-group has-error"> <!-- Email -->
<label for="email" class="control-label">E-mail</label>
<input type="text" class="form-control" id="email" name="email" placeholder="your@email.com">
<p id="email_error" class="help-block">Invalid email address.</p>
</div>
<div class="form-group has-error"> <!-- Zip Code -->
<label for="zipcode" class="control-label">Zip Code</label>
<input type="text" class="form-control" id="zipcode" name="zipcode" placeholder="#####">
<p id="zipcode_error" class="help-block">Invalid zip code.</p>
</div>
<div class="form-group has-error"> <!-- Password -->
<label for="password" class="control-label">Password</label>
<input type="text" class="form-control" id="password" name="password" placeholder="*****">
<p id="password_error" class="help-block">Invalid password.</p>
</div>
<div class="form-group has-error"> <!-- Register Button -->
<button type="submit" class="btn btn-primary">Register</button>
</div>
</form>
Here is the form with errors added for every field:
A reactive form is a bit different from template-driven forms by providing more predictability with synchronous access to the data model, immutability with observable operators, and change tracking through observable streams.
To use the reactive form, we must import the FormsModule & ReactiveFormsModule from the @angular/forms package and add it to our app.module.ts
Next, lets modify the input-user-data-form.component.
We’ll inject the formBuilder into the component for use in the ngOnInit life cycle method. FormBuilder a service that helps making forms easier.
The FormBuilder will create a FormGroup userForm with FormControls. Each FormControl has a default value and a set of Validators.
Think of the userForm as a schema for the actual values. It holds validation rules for fields inside the form.
We’ll add registered & submitted boolean flags to the Component. We’ll use these to indicate the current form state**.**
Also, we’ll create a validator function for every input, see invalidFirstName(), invalidLastName(), invalidEmail(), invalidZipcode(), invalidPassword().
A validator function will be used in markup to hide / show error messages for each field.
input-user-data-form.components.ts
import { Component, OnInit } from '@angular/core';
import { FormBuilder, FormGroup, FormControl, Validators } from '@angular/forms';
@Component({
selector: 'input-user-data-form',
templateUrl: './input-user-data-form.component.html',
styleUrls: ['./input-user-data-form.component.css']
})
export class InputUserDataFormComponent implements OnInit {
registered = false;
submitted = false;
userForm: FormGroup;
constructor(private formBuilder: FormBuilder)
{
}
invalidFirstName()
{
return (this.submitted && this.userForm.controls.first_name.errors != null);
}
invalidLastName()
{
return (this.submitted && this.userForm.controls.last_name.errors != null);
}
invalidEmail()
{
return (this.submitted && this.userForm.controls.email.errors != null);
}
invalidZipcode()
{
return (this.submitted && this.userForm.controls.zipcode.errors != null);
}
invalidPassword()
{
return (this.submitted && this.userForm.controls.password.errors != null);
}
ngOnInit()
{
this.userForm = this.formBuilder.group({
first_name: ['', Validators.required],
last_name: ['', Validators.required],
email: ['', [Validators.required, Validators.email]],
zipcode: ['', [Validators.required, Validators.pattern('^[0-9]{5}(?:-[0-9]{4})?$')]],
password: ['', [Validators.required, Validators.minLength(5), Validators.pattern('^(?=.*[a-z])(?=.*[A-Z])(?=.*[0-9])[a-zA-Z0-9]+$')]],
});
}
onSubmit()
{
this.submitted = true;
if(this.userForm.invalid == true)
{
return;
}
else
{
this.registered = true;
}
}
};
In the input-user-data-form.component.html, and for every Reactive form we’ll use a directive [formGroup]
to bind to userForm
variable we defined in the component
We’ll bind the onSubmit handler via the (ngSubmit)
directive.
To connect an HTML input element to a Reactive form we need to add formControlName
attribute to each of the form inputs.
We’ll use the *ngIf & [ngClass] directives to control error messages. The styles and validation markup will get displayed after user attempts to submit the form. This is controlled with [submitted]
property of the component.
After submitting the form, it will be validated every time user changes the input value, causing errors to show & hide dynamically.
input-user-data-form.component-02.html
<form [formGroup]="userForm" (ngSubmit)="onSubmit()">
<div class="form-group" [ngClass]="{ 'has-error': invalidFirstName() }"> <!-- First Name -->
<label for="first_name" class="control-label">First Name</label>
<input type="text" formControlName="first_name" class="form-control" id="first_name" name="first_name" placeholder="Martin">
<p *ngIf="invalidFirstName()" id="first_name_error" class="help-block">Invalid first name.</p>
</div>
<div class="form-group" [ngClass]="{ 'has-error': invalidLastName() }"> <!-- Last Name -->
<label for="last_name" class="control-label">Last Name</label>
<input type="text" formControlName="last_name" class="form-control" id="last_name" name="last_name" placeholder="Toha">
<p *ngIf="invalidLastName()" id="last_name_error" class="help-block">Invalid last name.</p>
</div>
<div class="form-group" [ngClass]="{ 'has-error': invalidEmail() }"> <!-- Email -->
<label for="email" class="control-label">E-mail</label>
<input type="text" formControlName="email" class="form-control" id="email" name="email" placeholder="your@email.com">
<p *ngIf="invalidEmail()" id="email_error" class="help-block">Invalid email address.</p>
</div>
<div class="form-group" [ngClass]="{ 'has-error': invalidZipcode() }"> <!-- Zip Code-->
<label for="zipcode" class="control-label">Zip Code</label>
<input type="text" formControlName="zipcode" class="form-control" id="zipcode" name="zipcode" placeholder="#####">
<p *ngIf="invalidZipcode()" id="zipcode_error" class="help-block">Invalid zip code.</p>
</div>
<div class="form-group" [ngClass]="{ 'has-error': invalidPassword() }"> <!-- Password -->
<label for="password" class="control-label">Password</label>
<input type="password" formControlName="password" class="form-control" id="password" name="password" placeholder="*****">
<p *ngIf="invalidPassword()" id="password_error" class="help-block">Invalid password.</p>
</div>
<div class="form-group has-error"> <!-- Register Button -->
<button type="submit" class="btn btn-primary">Register</button>
</div>
</form>
Here is what the form looks like initially:
And the form after filling out some fields with error:
Looks good so far! Lets continue with the next component.
The next Angular component will display user data. This will be a simple component that visualizes a data model passed into it.
Lets create a data model UserInfoModel in app/models, we’ll make it deserialize an object when its passed into the constructor.
export class UserInfoModel
{
guid: string;
customerUid: string;
first_name: string;
last_name: string;
email: string;
zipcode: string;
password: string;
constructor(obj: any = null)
{
if(obj != null)
{
Object.assign(this, obj);
}
}
}
The view display-user-data.component.html binds to the model via interpolation {{…}} and displays the information.
display-user-data.component.html
<legend>User Information</legend>
<div>
<div class="form-group row"> <!-- GUD -->
<label class="col-xs-6 col-form-label">GUID</label>
<div class="col-xs-6">{{user.guid}}</div>
</div>
<div class="form-group row"> <!-- Customer UID -->
<label class="col-xs-6 col-form-label">Customer UID</label>
<div class="col-xs-6">{{user.customerUid}}</div>
</div>
<div class="form-group row"> <!-- First Name -->
<label class="col-xs-6 col-form-label">First Name</label>
<div class="col-xs-6">{{user.first_name}}</div>
</div>
<div class="form-group row"> <!-- Last Name -->
<label class="col-xs-6 col-form-label">Last Name</label>
<div class="col-xs-6">{{user.last_name}}</div>
</div>
<div class="form-group row"> <!-- E-mail -->
<label class="col-xs-6 col-form-label">E-mail</label>
<div class="col-xs-6">{{user.email}}</div>
</div>
<div class="form-group row"> <!-- Zip Code -->
<label class="col-xs-6 col-form-label">Zip Code</label>
<div class="col-xs-6">{{user.zipcode}}</div>
</div>
<div class="form-group row"> <!-- Password -->
<label class="col-xs-6 col-form-label">Password</label>
<div class="col-xs-6">{{user.password}}</div>
</div>
</div>
And just for testing purposes, DisplayUserDataComponent class will assign some default values into the UserInfoModel
display-user-data.component.ts
import { Component, OnInit } from '@angular/core';
import {UserInfoModel} from '../models/userInfo'
@Component({
selector: 'display-user-data',
templateUrl: './display-user-data.component.html',
styleUrls: ['./display-user-data.component.css']
})
export class DisplayUserDataComponent implements OnInit {
user: UserInfoModel = new UserInfoModel({guid: "D21ds12x",
customerUid: "cust2dsa12dsa",
first_name: "John",
last_name: "Doe",
email: "email@email.com",
zipcode: 10283,
password: "Idasn2x2#"});
constructor() { }
ngOnInit()
{
}
}
Both of the pages look great!
Now, lets connect the Router into the AppComponent to establish a page flow
Our goal with routing is to have the InputUserDataFormComponent
rendered when the url is /
, and DisplayUserDataComponent
shown when the url is /user/:uid
First, lets setup the imports to @angular/router, then define an array routes of our paths and destination pages.
const routes: Routes = [
{
path: '',
component: InputUserDataFormComponent
},
{
path: 'user/:uid',
component: DisplayUserDataComponent
}
];
In the imports
add RouterModule.forRoot(routes)
import { BrowserModule } from '@angular/platform-browser';
import { NgModule } from '@angular/core';
import { ReactiveFormsModule, FormsModule } from '@angular/forms';
import { AppComponent } from './app.component';
import { InputUserDataFormComponent } from './input-user-data-form/input-user-data-form.component';
import { DisplayUserDataComponent } from './display-user-data/display-user-data.component';
import { Routes, RouterModule } from "@angular/router";
const routes: Routes = [
{
path: '',
component: InputUserDataFormComponent
},
{
path: 'user/:uid',
component: DisplayUserDataComponent
}
];
@NgModule({
declarations: [
AppComponent,
InputUserDataFormComponent,
DisplayUserDataComponent
],
imports: [
BrowserModule,
FormsModule,
ReactiveFormsModule,
RouterModule.forRoot(routes)
],
providers: [],
bootstrap: [AppComponent]
})
export class AppModule { }
Place the router-outlet
in the app.component.html
<div class="container-fluid">
<div class="row">
<div class="col-xs-12">
<router-outlet></router-outlet>
</div>
</div>
</div>
Now the initial “/” root page looks like this:
Type “/user/a01” in the address bar and you get the User Information page
All works as intended on the client! Now lets continue with creation of API endpoint.
We’ll use the express-generator-api to make a Node.js API quickly by generating a project.
Install express-generator:
npm install -g express-generator-api
Create the API:
express-api angular-node-express-api & cd angular-node-express-api
Install dependencies:
npm install
Тhe file structure generated should be the following:
At this point all the basics of an API have been implemented by the generator.
For example, body parser & cookie parser are part of the app.js. Here express will try identify any JSON data that comes into our application and parse it for us.
Next, we are going to make the following API endpoints.
/customer
will insert a new customer and return auto-incremented customer.id
/customer/:uid
will retrieve a single customer by customer uid
/generate_guid
will generate a tracking_guide that Angular UI will use when creating a new customer
Lets copy users.js to generate_uid.js just to have a basic router. We’ll modify this router to return a random uid
Install uid-safe, which generates a uid safe for cookies
npm install uid-safe
Include it in generate_uid.js
var uid = require('uid-safe')
And return it with the response
var express = require('express');
var uid = require('uid-safe');
var router = express.Router();
/* GET a guid. */
router.get('/', function(req, res, next)
{
var strUid = uid.sync(18);
res.json({guid: strUid});
});
module.exports = router;
We’ll need to hook up the generate_uid router in the app.js
app.use('/api/v1/generate_uid', generate_uid);
The route returns a JSON with the GUID. Great!
{"guid":"K7VPC3I9kxIJ4Ct2_2ZR7Xb1"}
For every API service I usually have a model for the data and a service that performs all CRUD operations with it; that way there is a level of abstraction between the API request, storage & validation, but also a good way to access the service from anywhere in the application.
In this example, we’ll simply store customer data in memory.
The service will increment a customer UID every time a new customer is created.
We’ll use that customer UID to retrieve the customer data as well.
Create the models directory and add the following model.customer.js in there.
class CustomerModel
{
constructor(uid, first_name, last_name, email, zipcode, password)
{
this.uid = uid;
this.first_name = first_name;
this.last_name = last_name;
this.email = email;
this.zipcode = zipcode;
this.password = password;
}
}
module.exports = CustomerModel;
Then, create services directory and add a service.customer.js in there.
CustomerService implements all the CRUD operations create, read, update and delete the CustomerModel. It uses the counter to increment the customer uid; and stores all the customers into the customers object.
It’s important to validate our data on the server as well as the client. I usually keep validation as part of the service object, which is either a separate method or part of the CRUD operation.
We’ll implement the validation using the fastest-validator library.
Install fastest-validator library:
npm install fastest-validator --save
Import it in the CustomerService service object and create an instance of the Validator with custom schema.
var validator = require('fastest-validator');
The Schema object contains all validation rules, which is then used by the Validator instance to validate data against it.
Then, we’ll need to notify UI if validation fails on the server. If that happens, the create operation will throw an Error with list of errors for every failed validation.
services\service.customer.js
The list of errors will propagate into the response, which will be handled by Angular to communicate an error.
const CustomerModel = require("../models/model.customer");
let Validator = require('fastest-validator');
let customers = {};
let counter = 0;
/* create an instance of the validator */
let customerValidator = new Validator();
/* use the same patterns as on the client to validate the request */
let namePattern = /([A-Za-z\-\’])*/;
let zipCodePattern = /^[0-9]{5}(?:-[0-9]{4})?$/;
let passwordPattern = /^(?=.*[a-z])(?=.*[A-Z])(?=.*[0-9])[a-zA-Z0-9]+$/;
/* customer validator shema */
const customerVSchema = {
guid: {type: "string", min: 3},
first_name: { type: "string", min: 1, max: 50, pattern: namePattern},
last_name: { type: "string", min: 1, max: 50, pattern: namePattern},
email: { type: "email", max: 75 },
zipcode: { type: "string", max: 5, pattern: zipCodePattern},
password: { type: "string", min: 2, max: 50, pattern: passwordPattern}
};
/* static customer service class */
class CustomerService
{
static create(data)
{
var vres = customerValidator.validate(data, customerVSchema);
/* validation failed */
if(!(vres === true))
{
let errors = {}, item;
for(const index in vres)
{
item = vres[index];
errors[item.field] = item.message;
}
throw {
name: "ValidationError",
message: errors
};
}
let customer = new CustomerModel(data.first_name, data.last_name, data.email, data.zipcode, data.password);
customer.uid = 'c' + counter++;
customers[customer.uid] = customer;
return customer;
}
static retrieve(uid)
{
if(customers[uid] != null)
{
return customers[uid];
}
else
{
throw new Error('Unable to retrieve a customer by (uid:'+ uid +')');
}
}
static update(uid, data)
{
if(customers[uid] != null)
{
const customer = customers[uid];
Object.assign(customer, data);
}
else
{
throw new Error('Unable to retrieve a customer by (uid:'+ cuid +')');
}
}
static delete(uid)
{
if(customers[uid] != null)
{
delete customers[uid];
}
else
{
throw new Error('Unable to retrieve a customer by (uid:'+ cuid +')');
}
}
}
module.exports = CustomerService;
Lets connect the CustomerService to express router.
We’ll be using the async / await, which is a better way to write asynchronous code. Previous options are callbacks and promises, in fact async/await is built on top of promises; but async / await make the code behave & read a little more like synchronous code.
In the following router we implement all the CRUD operations using the CustomerService singleton.
Take a look at the create operation, where we submit user data and how errors are propagated into the response via try / catch block. The code is easy to read.
var express = require('express');
var router = express.Router();
var CustomerService = require('../services/service.customer');
/* GET customer listing. */
router.get('/', async function(req, res, next)
{
res.json({error: "Invalid Customer UID."});
});
/* adds a new customer to the list */
router.post('/', async (req, res, next) =>
{
const body = req.body;
try
{
const customer = await CustomerService.create(body);
if(body.guid != null)
{
customer.guid = body.guid;
}
res.cookie('guid', customer.guid, { maxAge: 900000, httpOnly: true });
// created the customer!
return res.status(201).json({ customer: customer });
}
catch(err)
{
if (err.name === 'ValidationError')
{
return res.status(400).json({ error: err.message });
}
// unexpected error
return next(err);
}
});
/* retrieves a customer by uid */
router.get('/:id', async (req, res, next) =>
{
try
{
const customer = await CustomerService.retrieve(req.params.id);
return res.json({ customer: customer });
}
catch(err)
{
// unexpected error
return next(err);
}
});
/* updates the customer by uid */
router.put('/:id', async (req, res, next) =>
{
try
{
const customer = await CustomerService.update(req.params.id, req.body);
return res.json({ customer: customer });
}
catch(err)
{
// unexpected error
return next(err);
}
});
/* removes the customer from the customer list by uid */
router.delete('/:id', async (req, res, next) =>
{
try
{
const customer = await CustomerService.delete(req.params.id);
return res.json({success: true});
}
catch(err)
{
// unexpected error
return next(err);
}
});
module.exports = router;
Next, we’ll need to modify the input-user-data-form.component & its template to support showing the server side errors, in case the validation fails on the server.
In the InputUserDataFormComponent we’ll add the serviceErrors object, which will contain all the server side errors for each fields. And add to the validator methods to check if the error message for that field exists, like so:
app\input-user-data-form.component.ts
We’ll also modify the onSubmit method, and add an error handler to our request which will simply set serviceErrors object.
app\input-user-data-form\input-user-data-form.component.ts
Next we’ll add a reference to server side errors in the input-user-data-form.component.html template to display a server side error in case it exists:
app\input-user-data-form\input-user-data-form.component.html
Now, we’ll know if validation fails on the server, since messages are going to be propagated to Angular UI.
Everything looks good, lets connect our routers in the app.js
var express = require('express');
var path = require('path');
var cookieParser = require('cookie-parser');
var bodyParser = require('body-parser');
var generate_uid = require('./routes/generate_uid');
var customer = require('./routes/customer');
var app = express();
app.use(bodyParser.json());
app.use(bodyParser.urlencoded({ extended: false }));
app.use(cookieParser())
app.use('/api/v1/customer', customer);
app.use('/api/v1/generate_uid', generate_uid);
module.exports = app;
We are done creating the application, now a couple of minor details.
We are using a proxy in order to go around the CORS browser issue by having the Webpack on port 4200 communicate with Node.js server on port 3000. This is a good solution for the development environment, but we’ll need to have a better implementation when moving to production.
The API server will need to either enable the API for all origins or white list our access point.
To enable our API for all is easy, just add the following code to app.js
app.use(function(req, res, next) {
res.header("Access-Control-Allow-Origin", "*");
res.header("Access-Control-Allow-Headers", "Origin, X-Requested-With, Content-Type, Accept");
next();
});
Another minor detail we haven’t covered is handling of Uncaught Exceptions
Because Node.js runs on a single processor uncaught exceptions are an issue to be aware of when developing applications.
When your application throws an uncaught exception you should consider that your application is now running in an unclean state. You can’t reliably continue your program at this point because you don’t really know what got affected by the error.
The best way to handle a crash is to collect as much data about it, send the errors to an external crash service or log it; and restart the server.
For our simple application, we’ll implement the appropriate functions, just place these in the beginning of your app.js
I’ll keep the reporter method empty, which we will connect in a later article to an external crash service
let reporter = function (type, ...rest)
{
// remote reporter logic goes here
};
/* handle an uncaught exception & exit the process */
process.on('uncaughtException', function (err)
{
console.error((new Date).toUTCString() + ' uncaughtException:', err.message);
console.error(err.stack);
reporter("uncaughtException", (new Date).toUTCString(), err.message, err.stack);
process.exit(1);
});
/* handle an unhandled promise rejection */
process.on('unhandledRejection', function (reason, promise)
{
console.error('unhandled rejection:', reason.message || reason);
reporter("uncaughtException", (new Date).toUTCString(), reason.message || reason);
})
Finally! To start the API server:
npm start
Try hitting the http://localhost:3000/api/v1/generate_uid
or http://localhost:3000/api/v1/customer
And you should see some JSON data.
To quickly integrate the Angular application we are going to:
Import & Inject HttpClient & Router into the InputUserDataFormComponent
Next, we’ll retrieve the GUID from the ‘/api/v1/generate_uid’ API service in the constructor of the InputUserDataFormComponent and set the guid variable
constructor of InputUserDataFormComponent
In the onSubmit method of the InputUserDataFormComponent we’ll post the data into the ‘/api/v1/customer’ service & navigate the Angular Router to the next page /user/:id
The full source code:
input-user-data-form.component-wroute-api.ts
import { Component, OnInit } from '@angular/core';
import { FormBuilder, FormGroup, FormControl, Validators } from '@angular/forms';
import { HttpClient } from "@angular/common/http";
import { Router } from "@angular/router";
@Component({
selector: 'input-user-data-form',
templateUrl: './input-user-data-form.component.html',
styleUrls: ['./input-user-data-form.component.css']
})
export class InputUserDataFormComponent implements OnInit {
registered = false;
submitted = false;
userForm: FormGroup;
guid: string;
serviceErrors:any = {};
constructor(private formBuilder: FormBuilder, private http: HttpClient, private router: Router)
{
this.http.get('/api/v1/generate_uid').subscribe((data:any) => {
this.guid = data.guid;
}, error => {
console.log("There was an error generating the proper GUID on the server", error);
});
}
invalidFirstName()
{
return (this.submitted && (this.serviceErrors.first_name != null || this.userForm.controls.first_name.errors != null));
}
invalidLastName()
{
return (this.submitted && (this.serviceErrors.last_name != null || this.userForm.controls.last_name.errors != null));
}
invalidEmail()
{
return (this.submitted && (this.serviceErrors.email != null || this.userForm.controls.email.errors != null));
}
invalidZipcode()
{
return (this.submitted && (this.serviceErrors.zipcode != null || this.userForm.controls.zipcode.errors != null));
}
invalidPassword()
{
return (this.submitted && (this.serviceErrors.password != null || this.userForm.controls.password.errors != null));
}
ngOnInit()
{
this.userForm = this.formBuilder.group({
first_name: ['', [Validators.required, Validators.maxLength(50)]],
last_name: ['', [Validators.required, Validators.maxLength(50)]],
email: ['', [Validators.required, Validators.email, Validators.maxLength(75)]],
zipcode: ['', [Validators.required, Validators.pattern('^[0-9]{5}(?:-[0-9]{4})?$')]],
password: ['', [Validators.required, Validators.minLength(5), Validators.pattern('^(?=.*[a-z])(?=.*[A-Z])(?=.*[0-9])[a-zA-Z0-9]+$')]],
});
}
onSubmit()
{
this.submitted = true;
if(this.userForm.invalid == true)
{
return;
}
else
{
let data: any = Object.assign({guid: this.guid}, this.userForm.value);
this.http.post('/api/v1/customer', data).subscribe((data:any) => {
let path = '/user/' + data.customer.uid;
this.router.navigate([path]);
}, error =>
{
this.serviceErrors = error.error.error;
});
this.registered = true;
}
}
};
Then lets Import & Inject HttpClient & ActivatedRoute into the DisplayUserDataComponent
Retrieve customer data from the ‘/api/v1/customer/:id’ API and populate the UserInfoModel with new data, and have DisplayUserDataComponent view redraw itself with new data via interpolation {{…}}
display-user-data.component-wroute-api.ts
import { Component, OnInit } from '@angular/core';
import {UserInfoModel} from '../models/userInfo';
import { HttpClient } from "@angular/common/http";
import { ActivatedRoute } from '@angular/router';
@Component({
selector: 'display-user-data',
templateUrl: './display-user-data.component.html',
styleUrls: ['./display-user-data.component.css']
})
export class DisplayUserDataComponent implements OnInit
{
user: UserInfoModel = new UserInfoModel({guid: "D21ds12x",
uid: "cust2dsa12dsa",
first_name: "John",
last_name: "Doe",
email: "email@email.com",
zipcode: 10283,
password: "Idasn2x2#"});
constructor(private http: HttpClient, private route: ActivatedRoute) {
}
private subscriber: any;
ngOnInit()
{
this.subscriber = this.route.params.subscribe(params => {
this.http.get('/api/v1/customer/' + params.uid).subscribe((data:any) => {
this.user = new UserInfoModel(data.customer);
});
});
}
}
The initial page of the application ‘/’:
Fill in the form and press Register:
Next page, the user information is displayed.
After creating a customer, you can also type in the customer url followed by customer uid to retrieve customer data:
http://localhost:3000/api/v1/customer/c0
{"customer":{"first_name":"John","last_name":"Doe","email":"john.doe@gmail.com","zipcode":"12345","password":"Udsakln12dsa","uid":"c0","guid":"gCnqJdp3saMNPpJfXPj6DORy"}}
Angular UI:
https://github.com/jsmuster/angular-node-express
Node.js + Express API:
https://github.com/jsmuster/angular-node-express-api
#nodejs #angular #javascript #node-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
1593184320
What is Angular? What it does? How we implement it in a project? So, here are some basics of angular to let you learn more about angular.
Angular is a Typescript-based open-source front-end web application platform. The Angular Team at Google and a community of individuals and corporations lead it. Angular lets you extend HTML’s syntax to express your apps’ components clearly. The angular resolves challenges while developing a single page and cross-platform applications. So, here the meaning of the single-page applications in angular is that the index.html file serves the app. And, the index.html file links other files to it.
We build angular applications with basic concepts which are NgModules. It provides a compilation context for components. At the beginning of an angular project, the command-line interface provides a built-in component which is the root component. But, NgModule can add a number of additional components. These can be created through a template or loaded from a router. This is what a compilation context about.
Components are key features in Angular. It controls a patch of the screen called a view. A couple of components that we create on our own helps to build a whole application. In the end, the root component or the app component holds our entire application. The component has its business logic that it does to support the view inside the class. The class interacts with the view through an API of properties and methods. All the components added by us in the application are not linked to the index.html. But, they link to the app.component.html through the selectors. A component can be a component and not only a typescript class by adding a decorator @Component. Then, for further access, a class can import it. The decorator contains some metadata like selector, template, and style. Here’s an example of how a component decorator looks like:
@Component({
selector: 'app-root',
templateUrl: 'app.component.html',
styleUrls: ['app.component.scss']
})
Modules are the package of functionalities of our app. It gives Angular the information about which features does my app has and what feature it uses. It is an empty Typescript class, but we transform it by adding a decorator @NgModule. So, we have four properties that we set up on the object pass to @NgModule. The four properties are declarations, imports, providers, and bootstrap. All the built-in new components add up to the declarations array in @NgModule.
@NgModule({
declarations: [
AppComponent,
],
imports: [
BrowserModule,
HttpClientModule,
AppRoutingModule,
FormsModule
],
bootstrap: [AppComponent]
})
Data Binding is the communication between the Typescript code of the component and the template. So, we have different kinds of data binding given below:
#angular #javascript #tech blogs #user interface (ui) #angular #angular fundamentals #angular tutorial #basics of angular
1635917640
このモジュールでは、Rustでハッシュマップ複合データ型を操作する方法について説明します。ハッシュマップのようなコレクション内のデータを反復処理するループ式を実装する方法を学びます。演習として、要求された注文をループし、条件をテストし、さまざまなタイプのデータを処理することによって車を作成するRustプログラムを作成します。
錆遊び場は錆コンパイラにブラウザインタフェースです。言語をローカルにインストールする前、またはコンパイラが利用できない場合は、Playgroundを使用してRustコードの記述を試すことができます。このコース全体を通して、サンプルコードと演習へのPlaygroundリンクを提供します。現時点でRustツールチェーンを使用できない場合でも、コードを操作できます。
Rust Playgroundで実行されるすべてのコードは、ローカルの開発環境でコンパイルして実行することもできます。コンピューターからRustコンパイラーと対話することを躊躇しないでください。Rust Playgroundの詳細については、What isRust?をご覧ください。モジュール。
このモジュールでは、次のことを行います。
Rustのもう1つの一般的なコレクションの種類は、ハッシュマップです。このHashMap<K, V>
型は、各キーK
をその値にマッピングすることによってデータを格納しますV
。ベクトル内のデータは整数インデックスを使用してアクセスされますが、ハッシュマップ内のデータはキーを使用してアクセスされます。
ハッシュマップタイプは、オブジェクト、ハッシュテーブル、辞書などのデータ項目の多くのプログラミング言語で使用されます。
ベクトルのように、ハッシュマップは拡張可能です。データはヒープに格納され、ハッシュマップアイテムへのアクセスは実行時にチェックされます。
次の例では、書評を追跡するためのハッシュマップを定義しています。ハッシュマップキーは本の名前であり、値は読者のレビューです。
use std::collections::HashMap;
let mut reviews: HashMap<String, String> = HashMap::new();
reviews.insert(String::from("Ancient Roman History"), String::from("Very accurate."));
reviews.insert(String::from("Cooking with Rhubarb"), String::from("Sweet recipes."));
reviews.insert(String::from("Programming in Rust"), String::from("Great examples."));
このコードをさらに詳しく調べてみましょう。最初の行に、新しいタイプの構文が表示されます。
use std::collections::HashMap;
このuse
コマンドは、Rust標準ライブラリの一部HashMap
からの定義をcollections
プログラムのスコープに取り込みます。この構文は、他のプログラミング言語がインポートと呼ぶものと似ています。
HashMap::new
メソッドを使用して空のハッシュマップを作成します。reviews
必要に応じてキーと値を追加または削除できるように、変数を可変として宣言します。この例では、ハッシュマップのキーと値の両方がString
タイプを使用しています。
let mut reviews: HashMap<String, String> = HashMap::new();
このinsert(<key>, <value>)
メソッドを使用して、ハッシュマップに要素を追加します。コードでは、構文は<hash_map_name>.insert()
次のとおりです。
reviews.insert(String::from("Ancient Roman History"), String::from("Very accurate."));
ハッシュマップにデータを追加した後、get(<key>)
メソッドを使用してキーの特定の値を取得できます。
// Look for a specific review
let book: &str = "Programming in Rust";
println!("\nReview for \'{}\': {:?}", book, reviews.get(book));
出力は次のとおりです。
Review for 'Programming in Rust': Some("Great examples.")
ノート
出力には、書評が単なる「すばらしい例」ではなく「Some( "すばらしい例。")」として表示されていることに注意してください。get
メソッドはOption<&Value>
型を返すため、Rustはメソッド呼び出しの結果を「Some()」表記でラップします。
この.remove()
メソッドを使用して、ハッシュマップからエントリを削除できます。get
無効なハッシュマップキーに対してメソッドを使用すると、get
メソッドは「なし」を返します。
// Remove book review
let obsolete: &str = "Ancient Roman History";
println!("\n'{}\' removed.", obsolete);
reviews.remove(obsolete);
// Confirm book review removed
println!("\nReview for \'{}\': {:?}", obsolete, reviews.get(obsolete));
出力は次のとおりです。
'Ancient Roman History' removed.
Review for 'Ancient Roman History': None
このコードを試して、このRustPlaygroundでハッシュマップを操作できます。
演習:ハッシュマップを使用して注文を追跡する
この演習では、ハッシュマップを使用するように自動車工場のプログラムを変更します。
ハッシュマップキーと値のペアを使用して、車の注文に関する詳細を追跡し、出力を表示します。繰り返しになりますが、あなたの課題は、サンプルコードを完成させてコンパイルして実行することです。
この演習のサンプルコードで作業するには、次の2つのオプションがあります。
ノート
サンプルコードで、
todo!
マクロを探します。このマクロは、完了するか更新する必要があるコードを示します。
最初のステップは、既存のプログラムコードを取得することです。
car_quality
、car_factory
およびmain
機能を。次のコードをコピーしてローカル開発環境で編集する
か、この準備されたRustPlaygroundでコードを開きます。
#[derive(PartialEq, Debug)]
struct Car { color: String, motor: Transmission, roof: bool, age: (Age, u32) }
#[derive(PartialEq, Debug)]
enum Transmission { Manual, SemiAuto, Automatic }
#[derive(PartialEq, Debug)]
enum Age { New, Used }
// Get the car quality by testing the value of the input argument
// - miles (u32)
// Return tuple with car age ("New" or "Used") and mileage
fn car_quality (miles: u32) -> (Age, u32) {
// Check if car has accumulated miles
// Return tuple early for Used car
if miles > 0 {
return (Age::Used, miles);
}
// Return tuple for New car, no need for "return" keyword or semicolon
(Age::New, miles)
}
// Build "Car" using input arguments
fn car_factory(order: i32, miles: u32) -> Car {
let colors = ["Blue", "Green", "Red", "Silver"];
// Prevent panic: Check color index for colors array, reset as needed
// Valid color = 1, 2, 3, or 4
// If color > 4, reduce color to valid index
let mut color = order as usize;
if color > 4 {
// color = 5 --> index 1, 6 --> 2, 7 --> 3, 8 --> 4
color = color - 4;
}
// Add variety to orders for motor type and roof type
let mut motor = Transmission::Manual;
let mut roof = true;
if order % 3 == 0 { // 3, 6, 9
motor = Transmission::Automatic;
} else if order % 2 == 0 { // 2, 4, 8, 10
motor = Transmission::SemiAuto;
roof = false;
} // 1, 5, 7, 11
// Return requested "Car"
Car {
color: String::from(colors[(color-1) as usize]),
motor: motor,
roof: roof,
age: car_quality(miles)
}
}
fn main() {
// Initialize counter variable
let mut order = 1;
// Declare a car as mutable "Car" struct
let mut car: Car;
// Order 6 cars, increment "order" for each request
// Car order #1: Used, Hard top
car = car_factory(order, 1000);
println!("{}: {:?}, Hard top = {}, {:?}, {}, {} miles", order, car.age.0, car.roof, car.motor, car.color, car.age.1);
// Car order #2: Used, Convertible
order = order + 1;
car = car_factory(order, 2000);
println!("{}: {:?}, Hard top = {}, {:?}, {}, {} miles", order, car.age.0, car.roof, car.motor, car.color, car.age.1);
// Car order #3: New, Hard top
order = order + 1;
car = car_factory(order, 0);
println!("{}: {:?}, Hard top = {}, {:?}, {}, {} miles", order, car.age.0, car.roof, car.motor, car.color, car.age.1);
// Car order #4: New, Convertible
order = order + 1;
car = car_factory(order, 0);
println!("{}: {:?}, Hard top = {}, {:?}, {}, {} miles", order, car.age.0, car.roof, car.motor, car.color, car.age.1);
// Car order #5: Used, Hard top
order = order + 1;
car = car_factory(order, 3000);
println!("{}: {:?}, Hard top = {}, {:?}, {}, {} miles", order, car.age.0, car.roof, car.motor, car.color, car.age.1);
// Car order #6: Used, Hard top
order = order + 1;
car = car_factory(order, 4000);
println!("{}: {:?}, Hard top = {}, {:?}, {}, {} miles", order, car.age.0, car.roof, car.motor, car.color, car.age.1);
}
2. プログラムをビルドします。次のセクションに進む前に、コードがコンパイルされて実行されることを確認してください。
次の出力が表示されます。
1: Used, Hard top = true, Manual, Blue, 1000 miles
2: Used, Hard top = false, SemiAuto, Green, 2000 miles
3: New, Hard top = true, Automatic, Red, 0 miles
4: New, Hard top = false, SemiAuto, Silver, 0 miles
5: Used, Hard top = true, Manual, Blue, 3000 miles
6: Used, Hard top = true, Automatic, Green, 4000 miles
現在のプログラムは、各車の注文を処理し、各注文が完了した後に要約を印刷します。car_factory
関数を呼び出すたびにCar
、注文の詳細を含む構造体が返され、注文が実行されます。結果はcar
変数に格納されます。
お気づきかもしれませんが、このプログラムにはいくつかの重要な機能がありません。すべての注文を追跡しているわけではありません。car
変数は、現在の注文の詳細のみを保持しています。関数car
の結果で変数が更新されるたびcar_factory
に、前の順序の詳細が上書きされます。
ファイリングシステムのようにすべての注文を追跡するために、プログラムを更新する必要があります。この目的のために、<K、V>ペアでハッシュマップを定義します。ハッシュマップキーは、車の注文番号に対応します。ハッシュマップ値は、Car
構造体で定義されているそれぞれの注文の詳細になります。
main
関数の先頭、最初の中括弧の直後に次のコードを追加します{
。// Initialize a hash map for the car orders
// - Key: Car order number, i32
// - Value: Car order details, Car struct
use std::collections::HashMap;
let mut orders: HashMap<i32, Car> = HashMap;
2. orders
ハッシュマップを作成するステートメントの構文の問題を修正します。
ヒント
ハッシュマップを最初から作成しているので、おそらくこの
new()
メソッドを使用することをお勧めします。
3. プログラムをビルドします。次のセクションに進む前に、コードがコンパイルされていることを確認してください。コンパイラからの警告メッセージは無視してかまいません。
次のステップは、履行された各自動車注文をハッシュマップに追加することです。
このmain
関数では、car_factory
車の注文ごとに関数を呼び出します。注文が履行された後、println!
マクロを呼び出して、car
変数に格納されている注文の詳細を表示します。
// Car order #1: Used, Hard top
car = car_factory(order, 1000);
println!("{}: {}, Hard top = {}, {:?}, {}, {} miles", order, car.age.0, car.roof, car.motor, car.color, car.age.1);
...
// Car order #6: Used, Hard top
order = order + 1;
car = car_factory(order, 4000);
println!("{}: {}, Hard top = {}, {:?}, {}, {} miles", order, car.age.0, car.roof, car.motor, car.color, car.age.1);
新しいハッシュマップで機能するように、これらのコードステートメントを修正します。
car_factory
関数の呼び出しは保持します。返された各Car
構造体は、ハッシュマップの<K、V>ペアの一部として格納されます。println!
マクロの呼び出しを更新して、ハッシュマップに保存されている注文の詳細を表示します。main
関数で、関数の呼び出しcar_factory
とそれに伴うprintln!
マクロの呼び出しを見つけます。// Car order #1: Used, Hard top
car = car_factory(order, 1000);
println!("{}: {}, Hard top = {}, {:?}, {}, {} miles", order, car.age.0, car.roof, car.motor, car.color, car.age.1);
...
// Car order #6: Used, Hard top
order = order + 1;
car = car_factory(order, 4000);
println!("{}: {}, Hard top = {}, {:?}, {}, {} miles", order, car.age.0, car.roof, car.motor, car.color, car.age.1);
2. すべての自動車注文のステートメントの完全なセットを次の改訂されたコードに置き換えます。
// Car order #1: Used, Hard top
car = car_factory(order, 1000);
orders(order, car);
println!("Car order {}: {:?}", order, orders.get(&order));
// Car order #2: Used, Convertible
order = order + 1;
car = car_factory(order, 2000);
orders(order, car);
println!("Car order {}: {:?}", order, orders.get(&order));
// Car order #3: New, Hard top
order = order + 1;
car = car_factory(order, 0);
orders(order, car);
println!("Car order {}: {:?}", order, orders.get(&order));
// Car order #4: New, Convertible
order = order + 1;
car = car_factory(order, 0);
orders(order, car);
println!("Car order {}: {:?}", order, orders.get(&order));
// Car order #5: Used, Hard top
order = order + 1;
car = car_factory(order, 3000);
orders(order, car);
println!("Car order {}: {:?}", order, orders.get(&order));
// Car order #6: Used, Hard top
order = order + 1;
car = car_factory(order, 4000);
orders(order, car);
println!("Car order {}: {:?}", order, orders.get(&order));
3. 今すぐプログラムをビルドしようとすると、コンパイルエラーが表示されます。<K、V>ペアをorders
ハッシュマップに追加するステートメントに構文上の問題があります。問題がありますか?先に進んで、ハッシュマップに順序を追加する各ステートメントの問題を修正してください。
ヒント
orders
ハッシュマップに直接値を割り当てることはできません。挿入を行うにはメソッドを使用する必要があります。
プログラムが正常にビルドされると、次の出力が表示されます。
Car order 1: Some(Car { color: "Blue", motor: Manual, roof: true, age: ("Used", 1000) })
Car order 2: Some(Car { color: "Green", motor: SemiAuto, roof: false, age: ("Used", 2000) })
Car order 3: Some(Car { color: "Red", motor: Automatic, roof: true, age: ("New", 0) })
Car order 4: Some(Car { color: "Silver", motor: SemiAuto, roof: false, age: ("New", 0) })
Car order 5: Some(Car { color: "Blue", motor: Manual, roof: true, age: ("Used", 3000) })
Car order 6: Some(Car { color: "Green", motor: Automatic, roof: true, age: ("Used", 4000) })
改訂されたコードの出力が異なることに注意してください。println!
マクロディスプレイの内容Car
各値を示すことによって、構造体と対応するフィールド名。
次の演習では、ループ式を使用してコードの冗長性を減らします。
for、while、およびloop式を使用します
多くの場合、プログラムには、その場で繰り返す必要のあるコードのブロックがあります。ループ式を使用して、繰り返しの実行方法をプログラムに指示できます。電話帳のすべてのエントリを印刷するには、ループ式を使用して、最初のエントリから最後のエントリまで印刷する方法をプログラムに指示できます。
Rustは、プログラムにコードのブロックを繰り返させるための3つのループ式を提供します。
loop
:手動停止が発生しない限り、繰り返します。while
:条件が真のままで繰り返します。for
:コレクション内のすべての値に対して繰り返します。この単元では、これらの各ループ式を見ていきます。
loop
式は、無限ループを作成します。このキーワードを使用すると、式の本文でアクションを継続的に繰り返すことができます。ループを停止させるための直接アクションを実行するまで、アクションが繰り返されます。
次の例では、「We loopforever!」というテキストを出力します。そしてそれはそれ自体で止まりません。println!
アクションは繰り返し続けます。
loop {
println!("We loop forever!");
}
loop
式を使用する場合、ループを停止する唯一の方法は、プログラマーとして直接介入する場合です。特定のコードを追加してループを停止したり、Ctrl + Cなどのキーボード命令を入力してプログラムの実行を停止したりできます。
loop
式を停止する最も一般的な方法は、break
キーワードを使用してブレークポイントを設定することです。
loop {
// Keep printing, printing, printing...
println!("We loop forever!");
// On the other hand, maybe we should stop!
break;
}
プログラムがbreak
キーワードを検出すると、loop
式の本体でアクションの実行を停止し、次のコードステートメントに進みます。
break
キーワードは、特別な機能を明らかにするloop
表現を。break
キーワードを使用すると、式本体でのアクションの繰り返しを停止することも、ブレークポイントで値を返すこともできます。
次の例はbreak
、loop
式でキーワードを使用して値も返す方法を示しています。
let mut counter = 1;
// stop_loop is set when loop stops
let stop_loop = loop {
counter *= 2;
if counter > 100 {
// Stop loop, return counter value
break counter;
}
};
// Loop should break when counter = 128
println!("Break the loop at counter = {}.", stop_loop);
出力は次のとおりです。
Break the loop at counter = 128.
私たちのloop
表現の本体は、これらの連続したアクションを実行します。
stop_loop
変数を宣言します。loop
式の結果にバインドするようにプログラムに指示します。loop
式の本体でアクションを実行します:counter
値を現在の値の2倍にインクリメントします。counter
値を確認してください。counter
値が100以上です。ループから抜け出し、
counter
値を返します。
4. もしcounter
値が100以上ではありません。
ループ本体でアクションを繰り返します。
5. stop_loop
値を式のcounter
結果である値に設定しますloop
。
loop
式本体は、複数のブレークポイントを持つことができます。式に複数のブレークポイントがある場合、すべてのブレークポイントは同じタイプの値を返す必要があります。すべての値は、整数型、文字列型、ブール型などである必要があります。ブレークポイントが明示的に値を返さない場合、プログラムは式の結果を空のタプルとして解釈します()
。
while
ループは、条件式を使用しています。条件式が真である限り、ループが繰り返されます。このキーワードを使用すると、条件式がfalseになるまで、式本体のアクションを実行できます。
while
ループは、ブール条件式を評価することから始まります。条件式がと評価されるtrue
と、本体のアクションが実行されます。アクションが完了すると、制御は条件式に戻ります。条件式がと評価されるfalse
と、while
式は停止します。
次の例では、「しばらくループします...」というテキストを出力します。ループを繰り返すたびに、「カウントが5未満である」という条件がテストされます。条件が真のままである間、式本体のアクションが実行されます。条件が真でなくなった後、while
ループは停止し、プログラムは次のコードステートメントに進みます。
while counter < 5 {
println!("We loop a while...");
counter = counter + 1;
}
for
ループは、項目のコレクションを処理するためにイテレータを使用しています。ループは、コレクション内の各アイテムの式本体のアクションを繰り返します。このタイプのループの繰り返しは、反復と呼ばれます。すべての反復が完了すると、ループは停止します。
Rustでは、配列、ベクトル、ハッシュマップなど、任意のコレクションタイプを反復処理できます。Rustはイテレータを使用して、コレクション内の各アイテムを最初から最後まで移動します。
for
ループはイテレータとして一時変数を使用しています。変数はループ式の開始時に暗黙的に宣言され、現在の値は反復ごとに設定されます。
次のコードでは、コレクションはbig_birds
配列であり、イテレーターの名前はbird
です。
let big_birds = ["ostrich", "peacock", "stork"];
for bird in big_birds
iter()
メソッドを使用して、コレクション内のアイテムにアクセスします。for
式は結果にイテレータの現在の値をバインドするiter()
方法。式本体では、イテレータ値を操作できます。
let big_birds = ["ostrich", "peacock", "stork"];
for bird in big_birds.iter() {
println!("The {} is a big bird.", bird);
}
出力は次のとおりです。
The ostrich is a big bird.
The peacock is a big bird.
The stork is a big bird.
イテレータを作成するもう1つの簡単な方法は、範囲表記を使用することですa..b
。イテレータはa
値から始まりb
、1ステップずつ続きますが、値を使用しませんb
。
for number in 0..5 {
println!("{}", number * 2);
}
このコードは、0、1、2、3、および4の数値をnumber
繰り返し処理します。ループの繰り返しごとに、値を変数にバインドします。
出力は次のとおりです。
0
2
4
6
8
このコードを実行して、このRustPlaygroundでループを探索できます。
演習:ループを使用してデータを反復処理する
この演習では、自動車工場のプログラムを変更して、ループを使用して自動車の注文を反復処理します。
main
関数を更新して、注文の完全なセットを処理するためのループ式を追加します。ループ構造は、コードの冗長性を減らすのに役立ちます。コードを簡素化することで、注文量を簡単に増やすことができます。
このcar_factory
関数では、範囲外の値での実行時のパニックを回避するために、別のループを追加します。
課題は、サンプルコードを完成させて、コンパイルして実行することです。
この演習のサンプルコードで作業するには、次の2つのオプションがあります。
ノート
サンプルコードで、
todo!
マクロを探します。このマクロは、完了するか更新する必要があるコードを示します。
前回の演習でプログラムコードを閉じた場合は、この準備されたRustPlaygroundでコードを再度開くことができます。
必ずプログラムを再構築し、コンパイラエラーなしで実行されることを確認してください。
より多くの注文をサポートするには、プログラムを更新する必要があります。現在のコード構造では、冗長ステートメントを使用して6つの注文をサポートしています。冗長性は扱いにくく、維持するのが困難です。
ループ式を使用してアクションを繰り返し、各注文を作成することで、構造を単純化できます。簡略化されたコードを使用すると、多数の注文をすばやく作成できます。
main
機能、削除次の文を。このコードブロックは、order
変数を定義および設定し、自動車の注文のcar_factory
関数とprintln!
マクロを呼び出し、各注文をorders
ハッシュマップに挿入します。// Order 6 cars
// - Increment "order" after each request
// - Add each order <K, V> pair to "orders" hash map
// - Call println! to show order details from the hash map
// Initialize order variable
let mut order = 1;
// Car order #1: Used, Hard top
car = car_factory(order, 1000);
orders.insert(order, car);
println!("Car order {}: {:?}", order, orders.get(&order));
...
// Car order #6: Used, Hard top
order = order + 1;
car = car_factory(order, 4000);
orders.insert(order, car);
println!("Car order {}: {:?}", order, orders.get(&order));
2. 削除されたステートメントを次のコードブロックに置き換えます。
// Start with zero miles
let mut miles = 0;
todo!("Add a loop expression to fulfill orders for 6 cars, initialize `order` variable to 1") {
// Call car_factory to fulfill order
// Add order <K, V> pair to "orders" hash map
// Call println! to show order details from the hash map
car = car_factory(order, miles);
orders.insert(order, car);
println!("Car order {}: {:?}", order, orders.get(&order));
// Reset miles for order variety
if miles == 2100 {
miles = 0;
} else {
miles = miles + 700;
}
}
3. アクションを繰り返すループ式を追加して、6台の車の注文を作成します。order
1に初期化された変数が必要です。
4. プログラムをビルドします。コードがエラーなしでコンパイルされることを確認してください。
次の例のような出力が表示されます。
Car order 1: Some(Car { color: "Blue", motor: Manual, roof: true, age: ("New", 0) })
Car order 2: Some(Car { color: "Green", motor: SemiAuto, roof: false, age: ("Used", 700) })
Car order 3: Some(Car { color: "Red", motor: Automatic, roof: true, age: ("Used", 1400) })
Car order 4: Some(Car { color: "Silver", motor: SemiAuto, roof: false, age: ("Used", 2100) })
Car order 5: Some(Car { color: "Blue", motor: Manual, roof: true, age: ("New", 0) })
Car order 6: Some(Car { color: "Green", motor: Automatic, roof: true, age: ("Used", 700) })
プログラムは現在、ループを使用して6台の車の注文を処理しています。6台以上注文するとどうなりますか?
main
関数のループ式を更新して、11台の車を注文します。 todo!("Update the loop expression to create 11 cars");
2. プログラムを再構築します。実行時に、プログラムはパニックになります!
Compiling playground v0.0.1 (/playground)
Finished dev [unoptimized + debuginfo] target(s) in 1.26s
Running `target/debug/playground`
thread 'main' panicked at 'index out of bounds: the len is 4 but the index is 4', src/main.rs:34:29
この問題を解決する方法を見てみましょう。
このcar_factory
関数では、if / else式を使用color
して、colors
配列のインデックスの値を確認します。
// Prevent panic: Check color index for colors array, reset as needed
// Valid color = 1, 2, 3, or 4
// If color > 4, reduce color to valid index
let mut color = order as usize;
if color > 4 {
// color = 5 --> index 1, 6 --> 2, 7 --> 3, 8 --> 4
color = color - 4;
}
colors
配列には4つの要素を持ち、かつ有効なcolor
場合は、インデックスの範囲は0〜3の条件式をチェックしているcolor
私たちはをチェックしません(インデックスが4よりも大きい場合color
、その後の関数で4に等しいインデックスへのときに我々のインデックスを車の色を割り当てる配列では、インデックス値から1を減算しますcolor - 1
。color
値4はcolors[3]
、配列と同様に処理されます。)
現在のif / else式は、8台以下の車を注文するときの実行時のパニックを防ぐためにうまく機能します。しかし、11台の車を注文すると、プログラムは9番目の注文でパニックになります。より堅牢になるように式を調整する必要があります。この改善を行うために、別のループ式を使用します。
car_factory
機能、ループ式であれば/他の条件文を交換してください。color
インデックス値が4より大きい場合に実行時のパニックを防ぐために、次の擬似コードステートメントを修正してください。// Prevent panic: Check color index, reset as needed
// If color = 1, 2, 3, or 4 - no change needed
// If color > 4, reduce to color to a valid index
let mut color = order as usize;
todo!("Replace `if/else` condition with a loop to prevent run-time panic for color > 4");
ヒント
この場合、if / else条件からループ式への変更は実際には非常に簡単です。
2. プログラムをビルドします。コードがエラーなしでコンパイルされることを確認してください。
次の出力が表示されます。
Car order 1: Some(Car { color: "Blue", motor: Manual, roof: true, age: ("New", 0) })
Car order 2: Some(Car { color: "Green", motor: SemiAuto, roof: false, age: ("Used", 700) })
Car order 3: Some(Car { color: "Red", motor: Automatic, roof: true, age: ("Used", 1400) })
Car order 4: Some(Car { color: "Silver", motor: SemiAuto, roof: false, age: ("Used", 2100) })
Car order 5: Some(Car { color: "Blue", motor: Manual, roof: true, age: ("New", 0) })
Car order 6: Some(Car { color: "Green", motor: Automatic, roof: true, age: ("Used", 700) })
Car order 7: Some(Car { color: "Red", motor: Manual, roof: true, age: ("Used", 1400) })
Car order 8: Some(Car { color: "Silver", motor: SemiAuto, roof: false, age: ("Used", 2100) })
Car order 9: Some(Car { color: "Blue", motor: Automatic, roof: true, age: ("New", 0) })
Car order 10: Some(Car { color: "Green", motor: SemiAuto, roof: false, age: ("Used", 700) })
Car order 11: Some(Car { color: "Red", motor: Manual, roof: true, age: ("Used", 1400) })
このモジュールでは、Rustで使用できるさまざまなループ式を調べ、ハッシュマップの操作方法を発見しました。データは、キーと値のペアとしてハッシュマップに保存されます。ハッシュマップは拡張可能です。
loop
手動でプロセスを停止するまでの式は、アクションを繰り返します。while
式をループして、条件が真である限りアクションを繰り返すことができます。このfor
式は、データ収集を反復処理するために使用されます。
この演習では、自動車プログラムを拡張して、繰り返されるアクションをループし、すべての注文を処理しました。注文を追跡するためにハッシュマップを実装しました。
このラーニングパスの次のモジュールでは、Rustコードでエラーと障害がどのように処理されるかについて詳しく説明します。
リンク: https://docs.microsoft.com/en-us/learn/modules/rust-loop-expressions/
1597736283
Looking to build dynamic, extensively featured, and full-fledged web applications?
Hire NodeJs Developer to create a real-time, faster, and scalable application to accelerate your business. At HourlyDeveloper.io, we have a team of expert Node.JS developers, who have experience in working with Bootstrap, HTML5, & CSS, and also hold the knowledge of the most advanced frameworks and platforms.
Contact our experts: https://bit.ly/3hUdppS
#hire nodejs developer #nodejs developer #nodejs development company #nodejs development services #nodejs development #nodejs