Hi! we are updating the client with the last API changes, and we think that we have found an issue. The problem is related to the occupancyLevel field that is treated as string instead of integer. This causes that if a user make two reservations, the number of commensals are concatenated as a string instead of being added. The screenshot [reservation_5.png] shows the occupancyLevel after reserved five commensals while the [reservation_5_more.png] image shows the occupancyLevel after reserve five more commensals. The consequences of the issue are that neither the backend nor the front end can control the max reservations allowing to the app virtually make reservations for a infinite number of commensals.[allow_infinite_reservations.png] Any sugesttions? Regards, ULPGC team -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-developer-experience/attachments/20160215/232e95ab/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: allow_infinite_reservations.png Type: image/png Size: 52826 bytes Desc: not available URL: <https://lists.fiware.org/private/fiware-developer-experience/attachments/20160215/232e95ab/attachment.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: reservation_5_more.png Type: image/png Size: 46911 bytes Desc: not available URL: <https://lists.fiware.org/private/fiware-developer-experience/attachments/20160215/232e95ab/attachment-0001.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: reservation_5.png Type: image/png Size: 42149 bytes Desc: not available URL: <https://lists.fiware.org/private/fiware-developer-experience/attachments/20160215/232e95ab/attachment-0002.png>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy