We are using drag and drop extensively for creating virtual users in OctoPerf.
As I plan to migrate to Angular2, today I wanted to check how to handle drag and drop in the future of AngularJS.
I started from the W3Schools plain HTML / JS example and created the following component:
Immutable objects have multiple advantages over mutable objects which makes them the perfect building block to create software. You may already have many questions about the subject like:
You'll see in this article what an immutable object is, the advantages to use them every time you can and how they can speed up your software developments.
To make it simple, a class is immutable when instances of this class cannot be changed once constructed. Immutable objects follow five rules, like explained in Java Effective by Joshua Bloch:
No internal field can be reassigned after construction. This is very important: once the object has been constructed, there is no way to modify it.
public final class Truck {
private final String brand;
private final String model;
...
}
I'm still working on a Stripe administration console for OctoPerf, a SaaS performance testing tool. Stripe lets us manage our customers and their subscriptions.
I have a table that lists all of our customers (Customers.html):
<table class="table table-striped">
<thead class="thead-default">
<tr>
<th>#</th>
<th>Id</th>
<th>Email</th>
</tr>
</thead>
<tbody>
<tr *ngFor="#customer of customers; #i = index">
<th scope="row">{{i}}</th>
<td>{{customer.id}}</td>
<td>{{customer.email}}</td>
</tr>
</tbody>
</table>
It's an Angular2 application build using this excellent starter with BootStrap 4.
To follow up on my article about TypeScript generics in Angular2, I would like to unit test my Stripe client.
It involves mocking the Angular2 Http service, and it's far more complicated than unit testing the Router service. I first tried to inject a mock of the Http service and return custom Observable responses but this led to strange errors and cumbersome code.
I quickly switched to the recommended way, using MockBackend.
As a remainder, the service tested is a Stripe client. It makes recursive Http request to Stripe API in order to fetch customers and plans:
This post is an example of TypeScript generics usage, when writing an Angular2 application.
I'm working on a Stripe administration console. Stripe is a payment / subscription SaaS service that we use at OctoPerf.
I need to create pages that lists all our customers and plans. But Stripe returns paginated lists, and we need to do successive calls to their API to get the complete data. This mechanism is the same for both customers and plans lists. So we can factorise our code using generics in this particular case.
The first step is to create a common interface for customers and plans. They share a String id.
export interface HasId {
id:string;
}