[EPIC] Use blank strings instead of nullable strings in REST APIs
[EPIC] Future-proof AURA API (#192)
Parent:We have a lot of APIs that make use of nullable strings. This means a field can contain either a null
object or a string value. Usually having a nullable string adds no extra value compared allowing blank strings (""
). It does however make type errors much more likely in which string methods are called on null objects.
We should ditch nullable string fields and replace them with fields having a blank string default value and allowing blank values.
This issue follows a discussion in our mid-sprint meeting today.
Sub Tasks
-
Steering - @eigenwijsje - Use blank strings instead of nullable strings i... (steering#156 - closed) -
Tank - @eigenwijsje - Use blank strings instead of nullable strings i... (tank#58 - closed) -
Tank Cut & Glue - Use blank strings instead of nullable strings i... (tank-cut-glue#29 - closed) -
Dashboard - @kmohrf -
Engine API - Use blank strings instead of nullable strings i... (engine-api#42 - closed)
Edited by Ernesto Rico Schmidt