API process overly complicated and excessive redundancy
cweitat opened this issue · comments
-
API has alot of redundancy in information that is not needed such as attributes and heavily encapuslated within sub objects
Payment method details even on the page of browsing events
It's the backend job to parse the way they prefer; not make frontend to parse the way backend prefers.
FE should not be bearing the load of extracting information
-
Inconsistency usage of API headers resulting in a FE redundnacy code as mentioned here #8974
-
Unhelpful Response for API
Nobody needs to know the relations between each item; it has NO use cases at all -
Outdated documentation
APIs that were used are not documented at all