This will be a link to the map or design behind the change decisions.
Types of changes
What types of changes does your code introduce to Periodikal?
Put an x in the boxes that apply
[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices apply)
Checklist
_Put an x in the boxes that apply. You can also fill these out after creating the PR.
[ ] All apps build locally (npm run build:all)
[ ] Lint and unit tests pass locally with my changes
[ ] In the case of UI changes, I have locally verified no new browser console warnings were observed
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream modules
Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...
GIT RESOURCE: PR Template
Proposed changes
Implement CRUD Logic for other components
Link to Product Tracker
This will be a link to the issue you are specifically tasked with resolving.
Link to Figma/Zeplin
This will be a link to the map or design behind the change decisions.
Types of changes
What types of changes does your code introduce to Periodikal? Put an
xin the boxes that applyChecklist
_Put an
xin the boxes that apply. You can also fill these out after creating the PR.Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...
Screenshots if applicable
_Include screenshots in case of UI changes