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
Instead of sending a free-format "date", it would be cleaner to send back "startDate" and "endDate" in isoformat, and let the frontend decide how to render that.
The number of events to fetch should maybe be a GET parameter instead of being hardcoded to 5.
We should make an effort to keep names of things consistent between FE, API and BE where fields correspond to one another. Here that would mean renaming "subtitle" to "teaser" (and keeping the camel case for the date fields specified above).
All of this applies in particular if this isn't a one-off and we wanna start building an API. Also, I'm gonna do this in vanilla Django for now, but if we wanna do that, we should think about maybe using something like DRF.
"date"
, it would be cleaner to send back"startDate"
and"endDate"
in isoformat, and let the frontend decide how to render that.5
."subtitle"
to"teaser"
(and keeping the camel case for the date fields specified above).All of this applies in particular if this isn't a one-off and we wanna start building an API. Also, I'm gonna do this in vanilla Django for now, but if we wanna do that, we should think about maybe using something like DRF.
Originally posted by @ralokt in #141 (comment)
The text was updated successfully, but these errors were encountered: