Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
The `Rules` property should be made public
See original GitHub issueI want to be able to track each @import rule, while keeping the order of the other rules.
To make things more clear - think of @import as a C++ macro command (which in sort it actually is); what I want is to be able to get the entire CSS text. For that I need the Rules property (which is currently internal) to be made public. Then I could traverse all the rules, write each “simple” rule to a StringBuilder (for instance), and for each @import rule I encounter I will call the same method recursively.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@emiliano84 - Done. https://www.nuget.org/packages/ExCSS-Core/. Tried to contact @TylerBrinks via nuget and github, but no response. I would have preferred to be a contributer to this project than fork it.
Just to add to this - there are a lot of classes that are currently internal that should be public.
This pull request Fixed: StyleRule didn’t implement interface IStyleRule seems to have everything needed.
Please can you merge and publish to NuGet. The current NuGet package is unusable for me.
V2 of the lib was brilliant. It would be good to get V3 to the same level. 😃
If you are short on time, I’d be happy to contribute.