-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Convert Collection
to a function component
#2366
base: develop
Are you sure you want to change the base?
Conversation
Collection
to a function component
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.
Nicely Done
# Conflicts: # client/modules/User/components/Collection.jsx
collection: PropTypes.shape({ | ||
id: PropTypes.string, | ||
name: PropTypes.string, | ||
slug: PropTypes.string, | ||
description: PropTypes.string, | ||
owner: PropTypes.shape({ | ||
username: PropTypes.string | ||
}).isRequired, | ||
items: PropTypes.arrayOf(PropTypes.shape({})) | ||
}).isRequired, | ||
isOwner: PropTypes.bool.isRequired |
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.
@raclim it seemed like it made sense to pass down the collection
object from the parent component since the parent already has the object. But I find these prop types super annoying so idk, I may roll back some of the changes in the CollectionMetadata
file and access the collection with the useSelector
.
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.
That makes sense, it is pretty long! Thanks for the heads up!
Progress on #2358
Merge after #2253
Changes:
Collection
to a function component.I have verified that this pull request:
npm run lint
)npm run test
)develop
branch.Fixes #123