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
A user might browse an item with the name of the item. It is very similar to search among item, but here the handler is quicker and only searches among names of items t find the item. generating an HTTP request for browsing an item. The handler searches among items for finding the desired item. It is possible something be wrong and the function could not find the item, so the handler must return meaningful message. It is possible that a user wants to only view items and does not login into the online store (in this case the userId is null or empty, it should not check the validity of userId), so we do not have the information about the user , but when the user already logged in the system and tried to browse items, the handler should store a log object from the items that the user browsed, this log can be useful for future recommendations.
If any of the input arguments are empty or null, a 400 response should be returned with a description. The handler may make use of a 3rd party persistence library.
Important notes: the endpoint address is "/browseItems", the URL query parameters are: "userId" , "itemName"
The text was updated successfully, but these errors were encountered:
A user might browse an item with the name of the item. It is very similar to search among item, but here the handler is quicker and only searches among names of items t find the item. generating an HTTP request for browsing an item. The handler searches among items for finding the desired item. It is possible something be wrong and the function could not find the item, so the handler must return meaningful message. It is possible that a user wants to only view items and does not login into the online store (in this case the userId is null or empty, it should not check the validity of userId), so we do not have the information about the user , but when the user already logged in the system and tried to browse items, the handler should store a log object from the items that the user browsed, this log can be useful for future recommendations.
If any of the input arguments are empty or null, a 400 response should be returned with a description. The handler may make use of a 3rd party persistence library.
Important notes: the endpoint address is "/browseItems", the URL query parameters are: "userId" , "itemName"
The text was updated successfully, but these errors were encountered: