Open WillBrophy opened 10 years ago
@WillBrophy That's actually one of our tasks for this sprint, so we're working on it. We're in the process of making the API consistent with the code; we're just waiting until it's fully compiled before pushing it off to the front-ends.
the datetime keynames are different thoughout the API. for example - in meeting the date times are called datetime and endDatetime, but in get schedule it is called datetimeStart and datetimeEnd. could these be made consistent?