-
Notifications
You must be signed in to change notification settings - Fork 571
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
fixes for removeOptionalTags & ignoreCustomFragments #501
Conversation
So the trouble is with these lines, when both While fixing #500 I have also noticed the empty content cases for optional start tags are missing, so added those as well. |
@kangax I know it's been around forever, but should we be unconditionally trim whitespace of input to |
@kangax btw, it's been bugging me that |
treat any tags around non-HTML tags as mandatory fixes #503
@alexlamsl: you shouldn't mix unrelated commits. You should merge the unrelated patches to master. |
@XhmikosR @alexlamsl I agree that large-ish PR's are usually harder to land, since I tend to postpone reviewing them (when I don't have much time to look through all of it and understand; I just keep moving it for later). Small ones are definitely easier to understand and merge so if at all possible, unrelated changes are best extracted. And, as always, thanks for all the continuous help, folks! |
Wasn't certain about the process - will do for future maintenance commits that are trivial... Speaking of trivial commits, shall we land #498 before it gets really stale? |
Thanks a lot for the reviews so far - I know how hard it can be even for me to read my own code sometimes! |
@alexlamsl: so just rebase and move the following to a new branch and merge them separately https://github.com/alexlamsl/html-minifier/commit/49a4fa88ce1900a014bf9bc5d9cba730c5bd5281 Then see if you can squash some of the remaining patches when it makes sense. |
Let's see what I can do with git here... 😅 |
Closing for new PR(s) |
No description provided.