-
-
Notifications
You must be signed in to change notification settings - Fork 12
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
Add option to customize styles of the message box #3
Comments
I've added it here 9fb2184, but I'm not a JS programmer and could mess with code style, can you please help and review it? Also ci is failing after my changes: https://travis-ci.org/postcss/postcss-messages/jobs/56995895. |
CI is not failing anymore, I've figured our that there were unnecessary semicolons. |
messages({
style: {
'box-shadow': '0 0 10px black'
}
}); |
BTW, options is a lack in UX. You should better think more about default options and styles, rather than add options for every case. |
|
Done |
Inspired by postcss-messages. Then why not use that plugin? Well, look at the diff of index.js: - console.log(warningLog); + if (!('console' in options && !options.console)) { + console.log(warningLog); + } + + if (options.browser) { + result.root.append(formatBrowser(warningLog)); + } The only difference is how to display the warnings! There's no need to duplicate the rest of features between the two plugins. This fixes postcss/postcss-browser-reporter#8, postcss/postcss-browser-reporter#9 and postcss/postcss-browser-reporter#10. As opposed to postcss-messages, this implementation: - Inserts the messages at `head::before` instead of `html::before`. While `html::before` is unlikely to conflict with other styles, `head::before` is even less so! In fact, it should be _extremely_ unlikely to conflict. - Does not allow to change the selector. Because of the above point there's no need to. - Does not use `::after` if `::before` was already used in the CSS. Again, because of the first point there is no need to. - Does not allow to change the styling. There's no way to change the styling when logging to the console either. Also, @ai said: > BTW, options is a lack in UX. You should better think more about default > options and styles, rather than add options for every case. postcss/postcss-browser-reporter#3 (comment) - Uses simpler styling. KISS. It is still similar to postcss-messages.
Inspired by postcss-messages. Then why not use that plugin? Well, look at the diff of index.js: - console.log(warningLog); + if (!('console' in options && !options.console)) { + console.log(warningLog); + } + + if (options.browser) { + result.root.append(formatBrowser(warningLog)); + } The only difference is how to display the warnings! There's no need to duplicate the rest of features between the two plugins. This fixes postcss/postcss-browser-reporter#8, postcss/postcss-browser-reporter#9 and postcss/postcss-browser-reporter#10. As opposed to postcss-messages, this implementation: - Inserts the messages at `head::before` instead of `html::before`. While `html::before` is unlikely to conflict with other styles, `head::before` is even less so! In fact, it should be _extremely_ unlikely to conflict. - Does not allow to change the selector. Because of the above point there's no need to. - Does not use `::after` if `::before` was already used in the CSS. Again, because of the first point there is no need to. - Does not allow to change the styling. There's no way to change the styling when logging to the console either. Also, @ai said: > BTW, options is a lack in UX. You should better think more about default > options and styles, rather than add options for every case. postcss/postcss-browser-reporter#3 (comment) - Uses simpler styling. KISS. It is still similar to postcss-messages. - Properly escapes the CSS content string.
No description provided.
The text was updated successfully, but these errors were encountered: