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
Maybe it would be better to valorize the field anyway, with some kind of fallback value? For example deleted_user. Saves scripts breaking, having to add a lot of catch instructions, etc. This is more of a general hygiene question.
The text was updated successfully, but these errors were encountered:
In general, using the APIs with Python script is quite an unpleasant experience because the format of the responses to calls is so uneven. Maybe this is a problem that should be solved by the programmer, I don't know. But the problem is there.
Also, it accelerates bitrot. Any changes in the database (like the deletion of a user who authored annotations) risks introducing new variants in the format of the API response: in this case, some annotations now have a null value for creator_id`. So, a script that used to work when the data were complete in that sense now breaks.
For example this.
Maybe it would be better to valorize the field anyway, with some kind of fallback value? For example
deleted_user
. Saves scripts breaking, having to add a lot of catch instructions, etc. This is more of a general hygiene question.The text was updated successfully, but these errors were encountered: