Not Validating Custom Properties Causes Additional Issues

[blarosen95]

NOTE: This is related to #111 but is not the inherently the same issue.
As a result of not allowing custom properties to be validated by your validators, the closing curly brace can be returned as another parser error.
:root { --blue: #007bff; --indigo: #6610f2; --purple: #6f42c1; --pink: #e83e8c; --red: #dc3545; --orange: #fd7e14; --yellow: #ffc107; --green: #28a745; --teal: #20c997; --cyan: #17a2b8; --white: #fff; --gray: #6c757d; --gray-dark: #343a40; --primary: #12bbad; --secondary: #4f70ce; --success: #28a745; --info: #ccc; --warning: #ffc107; --danger: #dc3545; --light: #f3f3f3; --dark: #151515; --breakpoint-xs: 0; --breakpoint-sm: 576px; --breakpoint-md: 768px; --breakpoint-lg: 992px; --breakpoint-xl: 1200px; --font-family-sans-serif: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, "Helvetica Neue", Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol", "Noto Color Emoji"; --font-family-monospace: SFMono-Regular, Menlo, Monaco, Consolas, "Liberation Mono", "Courier New", monospace; }
Returns one parser error for every custom property, AND THEN it claims that the line containing "}" is invalid as well. It is no longer possible for your organization to claim a lack of pertinence in supporting custom properties.

[ylafon]

Fixed by #323