MATGONZALEZ: define default None in non required params in Routes for… #693
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The issue is the following
When looking to define non required params, the api builder doesn't give the option to define a default, so on some methods, the params are taking different than expect
Example:
when param is defined with
{ "name": "values",
"type": "[string]", "required": false}The route generation is:
values: root.scala.Option[List[String]And if in the call the param is not passed, the values red side the Controller code is
Some(List())instead of
None`The fix will add as default for every non required param a None as default in the route using the
?= None
part