-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
diag_field_not_found #1301
diag_field_not_found #1301
Conversation
…when registering fields
!< The field was not found in the table, so return diag_null | ||
fms_register_diag_field_obj = diag_null | ||
!< The field was not found in the table, so return DIAG_FIELD_NOT_FOUND | ||
fms_register_diag_field_obj = DIAG_FIELD_NOT_FOUND |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The doxygen \return needs to be updated to reflect this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The documentation for the function needs to be updated because it can return diag_field_not_found now
* Return diag_field_not_found if a field is not in the diag_table.yaml when registering fields
* Return diag_field_not_found if a field is not in the diag_table.yaml when registering fields
Description
Return diag_field_not_found if a field is not in the diag_table.yaml when registering fields.
This is needed to reproduce previous behavior and because there is code in MOM that expects the result to be diag_field_not_found.
Fixes # (issue)
How Has This Been Tested?
CI
Checklist:
make distcheck
passes