-
-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider using semantic HTML elements instead of <div/span> with classes #6
Comments
Hmm, yes I like this—but can the PR use both methods for now? And then I’ll make an issue to weigh whether or not to remove the classes in a major version change. Don’t want to break backwards compat there |
Hmm, replacing Either way, I’ll kick off a PR and we can take the discussion there. |
Looks like they were just Fixed by #7 |
Thinking a little bit more about this, I think it’s minimal risk here since we have provided both |
They became I don’t have a strong opinion. Version numbers are free, so when in doubt, it’s fine to use major bumps IMHO. |
Instead of using
<div>
s (or<span>
s) for marking parts of the code as highlighted/added/removed, why not just use semantic HTML elements?.highlight-line-active
→<mark>
.highlight-line-remove
→<del>
.highlight-line-add
→<ins>
Would you be open to a PR that makes this change?
The text was updated successfully, but these errors were encountered: