-
Notifications
You must be signed in to change notification settings - Fork 0
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
✨ - landing page implementation #38
Conversation
author Julian Roeland <[email protected]> 1715942902 +0200 committer Julian Roeland <[email protected]> 1716561398 +0200 :sparkles: - landing page implementation
16b8480
to
72af35b
Compare
One thing I forgot to mention: from the kanban page it should be possible to click on the destruction list and navigate to its detail page. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There were still a couple of questions from the previous review 😄
title: deslugify(status), | ||
items: constructComponentList(lists[status]), | ||
componentList: STATUSES.map((status) => ({ | ||
title: STATUS_LABELS[status] || deslugify(status), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the or
needed? Since it is hardcoded, we know that we have a label. Then we don't need to maintain the deslugify
function 😄
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a little bit surprised seeing api changes for the kanban as i expected only a minimal change. Also I don't see componentList
in @maykin-ui/admin-ui, is it missing a pr?
No description provided.