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
Send message page, there is program vouchers select for a specific account.
Programs page, there is voucher badge in a program card that demonstrates if program has any active vouchers.
We can use existing /vouchers request to obtain data required for them, however there are few limitations:
List in a response is paginated, only first n vouchers will be displayed by default. Since it's a select element, we can't really add pagination there, from a frontend perspective we can only change the design or specify higher limit.
Need to send two requests at the same time to display specific program vouchers and vouchers issued for all programs - one with programs: [programId] argument, and another one with programs: [] argument.
Not sure about this one, but feels like programs property in a reponse is always empty array, regardless if voucher is for programs and codes or codes only.
Possible Solution
Ideally, we can add two new requests to handle these use cases, or enhance the existing one.
The text was updated successfully, but these errors were encountered:
Problem to Solve
Based on #1629.
Send message page, there is program vouchers select for a specific account.
Programs page, there is voucher badge in a program card that demonstrates if program has any active vouchers.
We can use existing
/vouchers
request to obtain data required for them, however there are few limitations:n
vouchers will be displayed by default. Since it's a select element, we can't really add pagination there, from a frontend perspective we can only change the design or specify higher limit.programs: [programId]
argument, and another one withprograms: []
argument.programs
property in a reponse is always empty array, regardless if voucher is for programs and codes or codes only.Possible Solution
Ideally, we can add two new requests to handle these use cases, or enhance the existing one.
The text was updated successfully, but these errors were encountered: