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
I had a deep dive into the metadata the last days and noticed that the naming of timestamps is often unclear and the same name is used multiple times across the API. It might be helpful for a user to have a unique name for all values across the API. For example:
created_at -> entry_created_at
last_sync -> repository_last_sync
pushed_at -> latest_push_to_repo_at
I would also expose the pushed_at value at the top level, as this is likely to be a very important value for most users, showing the last time the project had any active development activity.
The text was updated successfully, but these errors were encountered:
I had a deep dive into the metadata the last days and noticed that the naming of timestamps is often unclear and the same name is used multiple times across the API. It might be helpful for a user to have a unique name for all values across the API. For example:
I would also expose the pushed_at value at the top level, as this is likely to be a very important value for most users, showing the last time the project had any active development activity.
The text was updated successfully, but these errors were encountered: