We are currently checking specifically against the most restrictive resource naming conventions rather than checking the validate inputs from all the resource steps that may be utilized individually. We should probably set it up so that we actually run the validate inputs from each resource step since they own this logic and we should only have to maintain this in one area.
The underlying task: We'll need to ensure a cohesive validation error message return across all the resources called. This may involve ensuring all messages follow the same [general] format and that the most restrictive steps are called first in the list.
We are currently checking specifically against the most restrictive resource naming conventions rather than checking the validate inputs from all the resource steps that may be utilized individually. We should probably set it up so that we actually run the validate inputs from each resource step since they own this logic and we should only have to maintain this in one area.
The underlying task: We'll need to ensure a cohesive validation error message return across all the resources called. This may involve ensuring all messages follow the same [general] format and that the most restrictive steps are called first in the list.