Uh oh!
There was an error while loading. Please reload this page.
Remove support for className prop - #799
Conversation
Users should wrap the `<Markdown>` component inside a `<div>` manually instead. Closes#781
This comment has been minimized.
This comment has been minimized.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@## main #799 +/- ##
=========================================
Coverage 100.00% 100.00% =========================================
Files 3 3 Lines 1354 1337 -17 Branches 113 110 -3 =========================================
- Hits 1354 1337 -17 ☔ View full report in Codecov by Sentry. |
remcohaszing
commented
Nov 17, 2023
I misinterpreted the meaning of the word deprecated here originally in a late evening. I interpret deprecated as planned for change or removal with a warning. In this project deprecated means removed with an error, making deprecations semver major. |
wooorm
commented
Nov 17, 2023
Can you drop the changelog entry? I’ll write the changelog/migration manually when the time is there! |
remcohaszing
commented
Nov 17, 2023
Sure 👍 It just feeld a bit weird to link a non-existent header from the code. |
wooorm
commented
Nov 17, 2023
Ah that’s why, hmm, then I’d do a |
remcohaszing
commented
Nov 17, 2023
Since this change is breaking, this PR shouldn’t be merged until the next major anyway. I think this PR thread is plenty reminder once this gets merged. :) |
This comment has been minimized.
This comment has been minimized.
wooorm
commented
Feb 20, 2025
Released in |
Initial checklist
Description of changes
This deprecates the
classNameprop, but does not remove it yet. Users should wrap the<Markdown>component inside a<div>manually instead.Closes#781