public static class UtilityParserTakes a class name apart into what it asks for.
No guide page documents this yet — the page shows what the code says about itself.
Remarks
The grammar is [variant:]*utility[-value][/opacity][!], and every one of those separators can also appear inside an arbitrary value. [&>*]:p-4 has a variant containing no colon but plenty of brackets; bg-[url(a/b.png)] has a slash that is not an opacity; content-['a:b'] has a colon that is not a variant separator. So every split here is bracket-aware, and the naive version of each one is a bug that only shows up on the arbitrary values people reach for precisely when nothing else will do.
Deliberately permissive about what a utility is: this only splits, and whether p-4 means anything is UtilityFamilies' question. Scanning is over-inclusive by design — a false positive costs one unused rule — so failing here has to mean "this is not shaped like a utility at all", never "I do not know this one".
Methods (1)
public static bool TryParse(string candidate, out UtilityCandidate parsed)Takes a class name apart.
Used by (3)
- ApplyExpanderVixen.Ui.Styling.Utilities
- UtilityFixtureVixen.Ui.Styling.Utilities.Tests
- UtilityGeneratorVixen.Ui.Styling.Utilities