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
Is your feature request related to a problem? Please describe.
We need to implement comment component UI for our app.
Note: Once Issue #103 is closed, only then should you work on this issue.
Describe the solution you'd like 1. Create an Comment.jsx component that should be located in src/app/components/profilepage/components/. * 2. Create an Comment.styles.js component ( note that we are using styled-components ) and make sure you are implementing the design using mobile-first approach ( mobile and up to desktop ) so we can prevent a lot of boilerplate css code and save us from media queries headaches.
You can work on this feature using a branch called feature/comment-component.
Pull Request Squashing
Please, go through these steps before you submit a PR.
Make sure that your PR is not a duplicate.
If not, then make sure that:
2.1. You have done your changes in a separate branch. Branches MUST have descriptive names that start with either the fix/ or feature/ prefixes. Good examples are: fix/signin-issue or feature/issue-templates.
2.2. You have a descriptive commit message with a short title (first line).
2.3. You have only one commit (if not, squash them into one commit).
2.4. npm test doesn't throw any error. If it does, fix them first and amend your commit (git commit --amend).
After these steps, you're ready to open a pull request.
3.1. Give a descriptive title to your PR.
3.2. Provide a description of your changes.
3.3. Put closes #XXXX in your comment to auto-close the issue that your PR fixes (if such).
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
We need to implement comment component UI for our app.
Note: Once Issue #103 is closed, only then should you work on this issue.
Describe the solution you'd like
1.
Create anComment.jsx
component that should be located insrc/app/components/profilepage/components/
. *2.
Create anComment.styles.js
component( note that we are using styled-components )
and make sure you are implementing the design using mobile-first approach (mobile and up to desktop
) so we can prevent a lot of boilerplate css code and save us from media queries headaches.You can work on this feature using a branch called
feature/comment-component
.Pull Request Squashing
Please, go through these steps before you submit a PR.
2.1. You have done your changes in a separate branch. Branches MUST have descriptive names that start with either the
fix/
orfeature/
prefixes. Good examples are:fix/signin-issue
orfeature/issue-templates
.2.2. You have a descriptive commit message with a short title (first line).
2.3. You have only one commit (if not, squash them into one commit).
2.4.
npm test
doesn't throw any error. If it does, fix them first and amend your commit (git commit --amend
).3.1. Give a descriptive title to your PR.
3.2. Provide a description of your changes.
3.3. Put
closes #XXXX
in your comment to auto-close the issue that your PR fixes (if such).The text was updated successfully, but these errors were encountered: