dc
eb9d4f555f
#560 merged with Clarity's emphasis module dropped from the curated entry file, and the eight spans that used Clarity's .badge classes are still there: two in the header actions (badge-danger, badge-info) and six in approve-details. The tip of release therefore renders those counters as plain text, since neither .dc-badge nor Clarity's .badge rules exist yet. .badge.badge-danger -> .dc-badge.dc-badge--danger .badge -> .dc-badge The replacement is app-owned and reads the design tokens Clarity read, so it follows the theme: utility-gray / utility-red / utility-blue for the background and typography-color-100 for the text, which light and dark redeclare. Measured in both themes against Clarity's own .badge on the same page before the switch: dark background rgb(174,184,188), text rgb(0,0,0) danger rgb(255,103,77), info rgb(102,209,255) light background rgb(79,97,105), text white danger rgb(224,34,0), info rgb(0,121,173) This is the badge half of #559, lifted out so the regression on release can be fixed without waiting for the tree work. Unit suite 1403 passing, tsc clean, production build clean.
Data Controller for SAS
Control your manual data modifications!
Alternatives to Data Controller include:
- 💾 Developing / testing / deploying / scheduling overnight batch jobs to load files from shared drives
- 🔒 Opening (and locking) datasets in Enterprise Guide or SAS® Table Viewer to perform direct updates
- ❓ Asking a #DBA to run validated code after a change management process
- 🌐 Building & maintaining your own custom web application
- 🏃 Running #SAS or #SQL updates in production
Problems with the above include:
- Legacy 'black box' solutions with little to no testing, documentation or support
- End users requiring direct write access to critical data sources in production
- Upload routines that must be manually modified when the data model changes
- Breaches due to unnecessary parties having access to the data
- Inability to trace who made a change, when, and why
- Reliance on key individuals to perform updates
- Building bespoke ETL for every new data source
- High risk of manual error / data corruption
Data Controller for SAS® solves all these issues in a simple-to-install, user-friendly, secure, documented, battle-tested web application. Available on Viya, SAS 9 EBI, and SASjs Server.
An individual Viya deploy can be done in just 2 lines of #SAS code!
filename dc url "https://git.datacontroller.io/dc/dc/releases/download/latest/viya.sas";
%inc dc;
For a multi-user deploy, using a shared system account, please see deploy docs.
For further information:
- Main site: https://datacontroller.io
- Docs: https://docs.datacontroller.io
- Code: https://code.datacontroller.io
For support, contact support@4gl.io or reach out on Matrix!
Development
Lighthouse CI
This project includes automated Lighthouse performance and accessibility checks that run on pull requests. The checks ensure:
- Accessibility Score: Minimum 1.0 (100%) median score across all tested pages
The Lighthouse CI workflow:
- Sets up the development environment with SASjs server and mocked services
- Builds and serves the Angular frontend
- Installs Chrome and runs
lhci autorun(Lighthouse CI) against key pages - Uploads results as artifacts for review
To run Lighthouse checks locally:
cd client
npm install
npm run lighthouse
Configuration is in client/lighthouserc.js (URL list, desktop preset, Chrome flags, assertions).