Replies: 3 comments
-
I don't think response codes is way to go - you would have to do some kind of site-specific mapping file between each status and a code for it. Adding more data to response would be my suggestion. |
Beta Was this translation helpful? Give feedback.
0 replies
-
That's why response codes exist though. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Improved an bit with response body in member but access denied in #297 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Currently Mulysa gives response body with member data for door query only when member has valid door access. For Vaasa Gatekeeper to report meaningful data in staff room, add response body for known members without door access too (currently HTTP 481 response).
Additionally we could define more codes for various states of member status, for example in style: Kuukausimaksu overdue == 283, Kuukausimaksu suspended == 483, etc. This way staff would know immediately who called to door, payment status and why it possibly failed.
Beta Was this translation helpful? Give feedback.
All reactions