This extension contains a couple of data models that should be available via configurable API endpoint. The extension t3api looks very promising in regards of integration and configuration.
Basic features
Models that should be available through API (GET):
Offer
User
Features
Offers (only public)
Categories
FeGroups
Bookmarks (private, via authentication)
It should be possible to filter and sort the response:
Offer
filter by search string
filter by Category
sort by different fields (crdate, title)
User
filter by search string
filter by Feature
filter by FeGroup
filter by Category
sort by different fields (username, email, crdate, name,..)
Creating entities
Creating and editing entities should be restricted to a logged-in fe_user. All models created (Offer, Feature, Bookmark,..) should be automatically associated with this user.
Evaluation of migrating the UserInfo DTO to t3api
There is a so called data transfer object "UserInfo" which contains aggregated data about all relevant infos about the currently logged-in user. This object is constructed inside the ApiController. It is to be investigated if this could be simplified by using the t3api extension.
This extension contains a couple of data models that should be available via configurable API endpoint. The extension t3api looks very promising in regards of integration and configuration.
Basic features
Models that should be available through API (GET):
It should be possible to filter and sort the response:
Creating entities
Creating and editing entities should be restricted to a logged-in
fe_user. All models created (Offer, Feature, Bookmark,..) should be automatically associated with this user.Evaluation of migrating the
UserInfoDTO to t3apiThere is a so called data transfer object "UserInfo" which contains aggregated data about all relevant infos about the currently logged-in user. This object is constructed inside the ApiController. It is to be investigated if this could be simplified by using the t3api extension.