-
Notifications
You must be signed in to change notification settings - Fork 29
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
Feat: bring up minifyUrls #98
Conversation
@@ -27,4 +27,5 @@ export default { | |||
removeRedundantAttributes: false, | |||
removeComments: 'safe', | |||
sortAttributesWithLists: true, | |||
minifyUrls: false, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
minifyUrls
should be considered as dangerous and shouldn't be enabled by default.
The option is not added in the max
preset either since it requires the user's configuration.
@SukkaW thanks a lot for these PRs! I highly appreciate your contributions to htmlnano! |
Thanks! Though, is there a reason to not include the docs updates in the same PR? |
Sure. Thanks! Then I'll wait with releasing a new version until that PR is merged as well. |
I'm not sure if my implementation will be accepted. There might also be a better implementation for the same feature, so I decide to split the document into another PR. I can include both implementation and the document change in one PR if you wish. |
Fair enough. Let's keep it that way then. |
The PR closes #10.
The document will be updated in another PR after this one is merged.
P.S.
I'm also refactoring
Object.keys
intoObject.entries
which will land in another PR. That PR should be included in the new release as well.