You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, a warning is given for all missing field. However, because it a lot of cases it does not make sense to fill every field. For example, in a sensor_view for a lidar sensor model, it does not make sense to output a warning, that the field "radar_sensor_view" is empty. But in that case I would still like to give a warning, if the (in this particular case) required field "lidar_sensor_view" is set.
Describe the solution you would like
Enable setting a rule "is_required" for specific field. This rule depends on the use case and cannot be automatically generated from the documentation in the proto files. (Unless some fields will be officially made mandatory in any case, as proposed in this issue: OpenSimulationInterface/open-simulation-interface#750)
Describe alternatives you have considered
Alternatively, I would remove the warning about empty fields at all, as there will most likely never be a case, where all existing fields in the entire interface are set.
Describe the backwards compatibility
It will break the behavior, that a warning is generated for every "missing" field. So there might be some backwards compatibility issues.
The text was updated successfully, but these errors were encountered:
Describe the feature
Currently, a warning is given for all missing field. However, because it a lot of cases it does not make sense to fill every field. For example, in a sensor_view for a lidar sensor model, it does not make sense to output a warning, that the field "radar_sensor_view" is empty. But in that case I would still like to give a warning, if the (in this particular case) required field "lidar_sensor_view" is set.
Describe the solution you would like
Enable setting a rule "is_required" for specific field. This rule depends on the use case and cannot be automatically generated from the documentation in the proto files. (Unless some fields will be officially made mandatory in any case, as proposed in this issue: OpenSimulationInterface/open-simulation-interface#750)
Describe alternatives you have considered
Alternatively, I would remove the warning about empty fields at all, as there will most likely never be a case, where all existing fields in the entire interface are set.
Describe the backwards compatibility
It will break the behavior, that a warning is generated for every "missing" field. So there might be some backwards compatibility issues.
The text was updated successfully, but these errors were encountered: