Address endpoints #105

Closed
opened 2021-01-15 22:00:30 +00:00 by niggl · 1 comment
Owner

We have to evaluate how to implement addresses in the most optimal way.
And then we have to implement them, ofc.

The prefered way would be as nested objects on tabels.

We have to evaluate how to implement addresses in the most optimal way. And then we have to implement them, ofc. The prefered way would be as nested objects on tabels.
niggl added this to the Contacts&Addresses milestone 2021-01-15 22:00:30 +00:00
niggl added the
enhancement
priority:medium
labels 2021-01-15 22:00:30 +00:00
niggl added a new dependency 2021-01-16 15:04:36 +00:00
niggl added the
status:doing
label 2021-01-16 15:04:49 +00:00
niggl referenced this issue from a commit 2021-01-16 15:57:59 +00:00
niggl referenced this issue from a commit 2021-01-16 15:58:57 +00:00
Author
Owner

Implementation: ✔
Manual tests: ✔

Onto implementing the addresses into existing tests for orgs and participants

Implementation: ✔ Manual tests: ✔ Onto implementing the addresses into existing tests for orgs and participants
niggl referenced this issue from a commit 2021-01-16 17:28:21 +00:00
niggl referenced this issue from a commit 2021-01-16 17:52:59 +00:00
niggl closed this issue 2021-01-16 20:42:29 +00:00
niggl referenced this issue from a commit 2021-01-19 14:48:08 +00:00
niggl reopened this issue 2021-01-19 15:12:29 +00:00
niggl closed this issue 2021-01-19 15:37:38 +00:00
niggl referenced this issue from a commit 2021-01-19 18:33:13 +00:00
Sign in to join this conversation.
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Blocks
Reference: lfk/backend#105
No description provided.