-
Notifications
You must be signed in to change notification settings - Fork 95
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
Component-ize Project documents (Doc::TileMedium
)
#459
Conversation
@@ -71,7 +71,7 @@ | |||
} | |||
|
|||
.overflow-button-container { | |||
@apply absolute right-1 top-1; | |||
@apply absolute right-1 top-1 z-10 h-[calc(100%-16px)] items-start; |
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.
The overflow-button gradient was still slightly visible even after #452
assert | ||
.dom(DOCUMENT_TYPE) | ||
.containsText(docType) | ||
.hasAttribute("href", "/documents?docType=%5B%22PRD%22%5D"); | ||
assert.dom(DOCUMENT_TYPE).containsText(docType); | ||
|
||
assert | ||
.dom(DOCUMENT_STATUS) | ||
.containsText(docStatus) | ||
.hasAttribute("href", "/documents?status=%5B%22Approved%22%5D"); | ||
assert.dom(DOCUMENT_STATUS).containsText(docStatus); |
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 removed interactivity from the status and docType tags. The use case for these filters isn't very strong, especially in comparison to docOwner/productArea — themselves debatable as links in this context — so as not to be worth sacrificing the click area.
Doc::TileMedium
)
Converts project-document code into a
Doc::TileMedium
component which can be used on other screens. Includes logic to load the ownerPhotos of newly added docs.(I imagine we'll eventually combine the
Doc::Tile
components but I'd like to handle that separately.)