[ ] Add a link to the related issue at the top of this description (above)
[ ] Connect this PR with the related issue via ZenHub with the button below this text box (or at the bottom of the page after the PR is created)
[ ] Ensure your branch is up to date with the target branch and resolve any conflicts
[ ] Answer the below questions to describe your PR for reviewers
[ ] Request at least two reviewers using the "Reviewers" section on the right, usually including at least one reviewer from your team
[ ] Notify the requested reviewers in the #code-review Slack channel once the PR is ready for review
Why are these changes needed?
In next.js applications using lodash's uniqueId causes "Props mismatch" warning to occur. Inputting a custom Id allows for the programmer to get rid of this warning.
What changed?
Add custom Id to all components, and use it in accordion.
Updated README.md with information about customId.
How are these changes tested?
Locally packaging it and running it in the patient app.
Issue:
PR Checklist
Why are these changes needed?
In next.js applications using lodash's uniqueId causes "Props mismatch" warning to occur. Inputting a custom Id allows for the programmer to get rid of this warning.
What changed?
Add custom Id to all components, and use it in accordion. Updated README.md with information about customId.
How are these changes tested?