You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the best way to create a "style guide" for ROAR apps to adhere to ensuring there aren't more css conflicts in the dashboard? Would it be possible to add a GitHub action that compare the roar-app css to the roar dashboard css for compliance/compatibility? In other words, could we set GitHub up to flag CSS issues for any PR on an app? Goal would be to force the developer to check for CSS issues and fix them before deploying in the dasbhoard and to try to urge usage of current CSS when possible
The text was updated successfully, but these errors were encountered:
Tagging @Willy-Chan here because he has 5 new apps that are ready to be implemented in the dashboard. Hopefully @Willy-Chan and @dguimara can sync up on a CSS plan for;
What is the best way to create a "style guide" for ROAR apps to adhere to ensuring there aren't more css conflicts in the dashboard? Would it be possible to add a GitHub action that compare the roar-app css to the roar dashboard css for compliance/compatibility? In other words, could we set GitHub up to flag CSS issues for any PR on an app? Goal would be to force the developer to check for CSS issues and fix them before deploying in the dasbhoard and to try to urge usage of current CSS when possible
The text was updated successfully, but these errors were encountered: