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
Now that we have the new data model with proper classes, we can significantly reduce code duplication for selector / badge components by writing them in a generic way.
As far as UI is concerned, we have the following kinds of objects:
Those with a name and an icon (Task, Skill, Shift)
Those with a name and an avatar (Person, Location)
Fallback: those that only have a name (Assignment?)
These can be represented as interfaces, and the components can be written like so:
Now that we have the new data model with proper classes, we can significantly reduce code duplication for selector / badge components by writing them in a generic way.
As far as UI is concerned, we have the following kinds of objects:
name
and anicon
(Task, Skill, Shift)name
and anavatar
(Person, Location)name
(Assignment?)These can be represented as interfaces, and the components can be written like so:
The text was updated successfully, but these errors were encountered: