Closed a-wong-8 closed 1 month ago
Name | Link |
---|---|
Latest commit | 83d2e591f0709934958ad5efd6af0825df2fc026 |
Latest deploy log | https://app.netlify.com/sites/adorable-fairy-ecd9fc/deploys/66d87ec78ce86d0008b81de3 |
Deploy Preview | https://deploy-preview-58--adorable-fairy-ecd9fc.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
Due to limited time, I'm not able to review the entire PR but this is what I gathered:
- I don't recommend adding HTML w/ Tailwind in metadata because we want separation of concern between metadata, HTML w/ Tailwind. If someone needed to update the styling, HTML, or debug, we want them to view and edit the React component, not the metadata. If there isn't a better solution, I would revert it to what it was before.
- Are there alternatives to using
dangerouslySetInnerHTML
? Based on research, it's typically avoided unless it's necessary. In the case of simply rendering static content in a modal, I would prefer using an alternative method of rendering content.- Accordion is misspelled.
@gevuong ok items corrected