Jan Peer Stöcklmair
Jan Peer Stöcklmair
Ya, those are good approaches and already had the same or similar approaches. In total I am more a fan of automation and less configuration. Here are my thoughts: 1....
I totally agree that it is risky in production. I guess this could work as you suggested in 1., replacing the code of `rcs.css()` with the selectors. In HTML however,...
Btw, the original issue with your HTML should be fixed in v`3.0.0`
No those elements are not yet removed. But this is actually a good feature. As I use Parse5 for HTML and PostCSS for AST it is not a big deal....
@klimashkin good point. Then it is also not a breaking change 👍
Hey @Stephen-X .. I won't have much time the next few weeks. The implementation of this feature will take some time, I hope you'll understand.
I am not sure if I understood it correctly, but I assume you meant something like following: Let's say we have two string in JavaScript, one with CSS selectors and...
The only bad thing is that there are a lot of modules which needs selectors, so everytime a new module is imported, which needs selectors, it must be included into...
@waterplea which version do you use?
You could also exclude `error` globally for such things: ```js import rcs from 'rcs-core'; // following methods also allow array of strings and RegExp rcs.selectorLibrary.setExclude('error'); // or rcs.selectorsLibrary.setExclude (if you...