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
Unfortunately I don't think the error messaging from the database will allow an automated "the public name is too long" error, I was able to track it down to a line that assigns a value to the public name, but the code doesn't see that.
Thus we need a better way for the in-cda validation system to report direct information like this to the user.
This would allow us to relate a given field to a specific column in the code so that things like "size limits" can be more distinctly reported to the user.
The text was updated successfully, but these errors were encountered:
So we currently have better support for validating user data, with the validation call on the CwmsDto.
However, it's clearly not quite enough. See #988.
Unfortunately I don't think the error messaging from the database will allow an automated "the public name is too long" error, I was able to track it down to a line that assigns a value to the public name, but the code doesn't see that.
Thus we need a better way for the in-cda validation system to report direct information like this to the user.
Given that https://github.com/USACE/cwms-data-api/blob/develop/cwms-data-api/src/main/java/cwms/cda/data/dto/CwmsDTOValidator.java#L54 already uses reflection to retrieve information, would it make sense to expand that system to also pull information, perhaps configured though additional annotations on the DTOs, from either the database or JOOQ.
This would allow us to relate a given field to a specific column in the code so that things like "size limits" can be more distinctly reported to the user.
The text was updated successfully, but these errors were encountered: