When using mockito to mock some methods behaviour, you may want to change your mocked method return value based on an argument value.
This is not obvious, but quite simple to achieve, thanks to this SO post. The following example show how to mock a call to the myMethod() function by returning the first string parameter.
when(mockObject.myMethod(anyString()))
.thenAnswer(invocation -> invocation.getArgument(0, String.class));Let’s say you want to make some enum values available to your Angular template. Angular binding cannot reference directly the enum value. A hack to work this around consists in adding to your component class a member variable initialized with the enum type.
Ex :
import { Component, Input, OnInit } from '@angular/core';
enum TransfertNature {Gerant, Etablissement, Autre};
@Component({
selector: 'app-transfert-siege',
templateUrl: './transfert-siege.component.html',
styleUrls: ['./transfert-siege.component.css']
})
export class TransfertSiegeComponent implements OnInit {
nature: TransfertNature;
TransfertNature: any = TransfertNature; // Can be used in the template
constructor() { }
ngOnInit(): void {
}
}
The Angular template will then be able to referece any value using the variable. Ex :
<ng-container [ngSwitch]="transfert.nature">
<ng-container *ngSwitchCase="TransfertNature.Gerant">
Spring Data can infer SQL queries from JpaRepository method name. That’s a great tool to uniformize query generations, and make code more readable. Obviously, this only works for simple SQL queries, wchich is indeed what you should strive for.
The documentation about the JpaRepository method naming convention is available here :
https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#jpa.query-methods
Key points :
When the following message is displayed by Visual Studio Code for an angular project, it’s time to switch from TSMint to ESLint, as TSLint has been deprecated for a while now.
Not using the local TSLint version found for 'c:/Users/nicol/Documents/GitHub/Bartleby/frontend/src/app/create-dossier/create-dossier.component.ts'
To enable code execution from the current workspace you must enable workspace library execution.This documentation from Microsoft describes the process : https://code.visualstudio.com/api/advanced-topics/tslint-eslint-migration