Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unify request/response types at the FacTec API client (remove the unused fields, clean up, extract more fields into shared structs, etc) #70

Closed
MOZGIII opened this issue Aug 11, 2021 · 0 comments · Fixed by #120
Assignees
Labels
facetec Related to FaceTec integration tech debt Technical debt
Milestone

Comments

@MOZGIII
Copy link
Contributor

MOZGIII commented Aug 11, 2021

No description provided.

@MOZGIII MOZGIII added the tech debt Technical debt label Aug 11, 2021
@MOZGIII MOZGIII changed the title Unify request/response types at the FacTec API client Unify request/response types at the FacTec API client (remove the unused field, clean up, extract more into shard structs, etc) Aug 11, 2021
@MOZGIII MOZGIII added this to the MVS milestone Aug 15, 2021
@MOZGIII MOZGIII added the facetec Related to FaceTec integration label Aug 15, 2021
@MOZGIII MOZGIII changed the title Unify request/response types at the FacTec API client (remove the unused field, clean up, extract more into shard structs, etc) Unify request/response types at the FacTec API client (remove the unused fields, clean up, extract more into shard structs, etc) Aug 16, 2021
@MOZGIII MOZGIII changed the title Unify request/response types at the FacTec API client (remove the unused fields, clean up, extract more into shard structs, etc) Unify request/response types at the FacTec API client (remove the unused fields, clean up, extract more fields into shared structs, etc) Aug 16, 2021
@tonycdot tonycdot self-assigned this Aug 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
facetec Related to FaceTec integration tech debt Technical debt
Development

Successfully merging a pull request may close this issue.

2 participants