Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
### Overview Two Issues: 1. The Alert's alignments were off (not centered and stretched out): The alignment Alert wasn't rendering properly because the alert was stretched vertically. Upon investigation, it was the X button that had a large height, despite the button seemingly set to "small" Looking into IconButton, seems like the size prop wasn't used, adding this prop back in seemed to fix the issue. --- 2. The border radius of both inline and general alerts should be 3px. ### PR Checklist - [ ] Related to designs: https://www.figma.com/design/ReGfRNillGABAj5SlITalN/%F0%9F%93%90-Gamut?node-id=30186-40358&m=dev - [ ] Related to JIRA ticket: [ABC-123] - [X] I have run this code to verify it works - [ ] This PR includes unit tests for the code change - [ ] This PR includes testing instructions tests for the code change - [ ] The alpha package of this PR is passing end-to-end tests in all relevant Codecademy repositories #### Testing Instructions 1. Go to `/docs/molecules-alert--usage-guidelines#alert-types` 2. Check that the height alignment matches [figma](https://www.figma.com/design/ReGfRNillGABAj5SlITalN/%F0%9F%93%90-Gamut?node-id=30186-40358&m=dev) #### PR Links and Envs | Repository | PR Link | PR Env | | :----------- | :------------------------------------------------------- | :------------------------------------------------------- | | Monolith | [Monolith PR](http://www.google.fr/ 'Named link title') | [Monolith Env](http://www.google.fr/ 'Named link title') | | Portal | [Portal Link](codecademy-engineering/mono#6915) | [Portal Env](http://www.google.fr/ 'Named link title') | | Another Repo | [Another Link](http://www.google.fr/ 'Named link title') | [Another Env](http://www.google.fr/ 'Named link title') | <!-- Merging your changes 1. Follow the [PR Title Guide](https://github.com/Codecademy/gamut#pr-title-guide), the title (which becomes the commit message) determines the version bump for the packages you changed. 3. Wrap the text describing your change in more detail in the "CHANGELOG-DESCRIPTION" comment tags above, this is what will show up in the changelog! 4. DO NOT MERGE MANUALLY! When you are ready to merge and publish your changes, add the "Ship It" label to your Pull Request. This will trigger the merge process as long as all checks have completed, if the checks haven't completed the branch will be merged when they all pass. **IMPORTANT:** If your PR contains breaking changes, please remember to follow the instructions for breaking changes! -->
- Loading branch information