Fix data modeling #1

Open
opened 2026-07-07 15:28:13 -05:00 by fenskesd · 0 comments
Owner

Problem Description:
Today a programmer might run into data model issues when working on the UI.

Example: A Habit object on the UI side appears to have habit logs on it. However, these are two separate data models requiring separate API calls. That's not obvious from looking at the data models in the repo.

Source of the Problem:
Our data models in the UI don't match up with what the API returns.

Proposed Solution:

  1. Represent the data models as the API does
  2. (Less good) Create a 2 tiered data model representation and an API responsible for pulling in the different pieces.
Problem Description: Today a programmer might run into data model issues when working on the UI. Example: A Habit object on the UI side appears to have habit logs on it. However, these are two separate data models requiring separate API calls. That's not obvious from looking at the data models in the repo. Source of the Problem: Our data models in the UI don't match up with what the API returns. Proposed Solution: 1. Represent the data models as the API does 2. (Less good) Create a 2 tiered data model representation and an API responsible for pulling in the different pieces.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
fenskesd/Steadfast-UI#1
No description provided.