# Perspective Style Class - Error Checking **URL:** \ **Category:** Ignition\ **Tags:** perspective\ **Created:** [August 17, 2022, 3:37pm UTC](https://forum.inductiveautomation.com/t/perspective-style-class-error-checking/63100 "2022-08-17T15:37:16Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![j.israelsen](https://avatars.discourse-cdn.com/v4/letter/j/ad7895/32.png) [@j.israelsen](https://forum.inductiveautomation.com/u/j.israelsen)\ **Post date:** [August 17, 2022, 3:37pm UTC](https://forum.inductiveautomation.com/t/perspective-style-class-error-checking/63100/1 "2022-08-17T15:37:16Z")
**Background:** We have had some issues where we setup a Style Class and find it does not work (it does not apply the style to the object). Come to find out it is because there was an error in our Style Class configuration (e.g. the Color setting was set to “FF8C00” when it should have been “#FF8C00”). **Question:** Is there an intuitive way to see that the style class has an error or to determine where the error in the Style Class is? ---
**Author:** ![cmallonee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmallonee/32/6416_2.png) [@cmallonee](https://forum.inductiveautomation.com/u/cmallonee)\ **Post date:** [August 17, 2022, 4:51pm UTC](https://forum.inductiveautomation.com/t/perspective-style-class-error-checking/63100/2 "2022-08-17T16:51:28Z")
Not really, no. Since css files are basically just text and don’t “compile” in the strictest sense, the only way to identify issues is by parsing it yourself or applying it and finding faults. Some text editors have extensions or plugins which _might_ help identify values that are strings which fit a hexadecimal pattern but which are missing a preceding `#`, but you’d have to search for that based on your preferred editor. Then you’d have to copy/paste your style into the editor to verify.