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
Gordon IDs in the database are currently either a string or an integer (depending on whether they came from the TmsEPrd or MyGordon databases). I think it would be best to make them consistent before they ever get to the API. Whether this means casting them to a string or an int, I am not sure. But it would be better to have them be the same datatype so that we do not have to write all of this logic to convert them back and forth in the API/UI.
The text was updated successfully, but these errors were encountered:
Gordon IDs in the database are currently either a string or an integer (depending on whether they came from the TmsEPrd or MyGordon databases). I think it would be best to make them consistent before they ever get to the API. Whether this means casting them to a string or an int, I am not sure. But it would be better to have them be the same datatype so that we do not have to write all of this logic to convert them back and forth in the API/UI.
The text was updated successfully, but these errors were encountered: