Migration of the parameters from study-server

[flomillot]

No description provided.

[SlimaneAmar]

Best pratices

1. Return optional if really optional else throw not found because it's difficult to understand the code
2. Reduce the checks null values, normally variables are nerver null or else it's optional
3. For null checks, on a method public add a Objects.requireNonNull or annotation NotNull and private methods we never check

[flomillot]

Best pratices

1. Return optional if really optional else throw not found because it's difficult to understand the code
2. Reduce the checks null values, normally variables are nerver null or else it's optional
3. For null checks, on a method public add a Objects.requireNonNull or annotation NotNull and private methods we never check

1. As done on loadflow-server and suggested here, I let ResponseEntity manage the return code
2. Which ones should I remove ? Because I used the same code as voltage-init which I were supposed to copy
   update
   assignAttributes
   Is it these ones I should remove ?
3. That's already the case, no ?

[AbdelHedhili]

code : ok, but can you check if you can resolve some sonar issue

[flomillot]

code : ok, but can you check if you can resolve some sonar issue

Unfortunately it's issues already present. For the number of params, it's allowed if it's for methods called by the controller if I remember well.

[sonarqubecloud]

Quality Gate passed

The SonarCloud Quality Gate passed, but some issues were introduced.

4 New issues
0 Security Hotspots
96.2% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud