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
The JSON export currently uses fields with different capitalization rules and sometimes even wording differences compared to the official API. For instance, timestampEdited and isPinned, which are subtly different from the official edited_timestamp and pinned. I feel like this is unnecessary and confusing for everybody who has to work with it. While it would be a breaking change for the project, I would seriously consider introducing consistency with official fields where possible.
The text was updated successfully, but these errors were encountered:
This is on purpose actually. There is no attempt to keep the field names in sync because DCE's domain representation is vastly different from the Discord's API in several places.
The JSON export currently uses fields with different capitalization rules and sometimes even wording differences compared to the official API. For instance,
timestampEdited
andisPinned
, which are subtly different from the officialedited_timestamp
andpinned
. I feel like this is unnecessary and confusing for everybody who has to work with it. While it would be a breaking change for the project, I would seriously consider introducing consistency with official fields where possible.The text was updated successfully, but these errors were encountered: