dc
ca157a307a
spreadsheet-util imports @sheet/crypto (1.75 MB: xlsx 958 kB, cpexcel 472 kB, jszip 323 kB) and buffer at module scope, and SpreadsheetService imported it statically, so the editor route downloaded the whole engine to draw a drop zone. The engine now sits behind a ChunkLoader that caches the load for the success path only, and SpreadsheetService awaits it in the two methods that need it. parseExcelSheetNames imports the engine inside the handler's try, because an async FileReader handler swallows its own rejection: a chunk that fails to load has to reject that promise or the caller waits on a dialog that never moves. Measured on the deployed build: the editor route loads 11 scripts with the engine chunk absent, and attaching a file to the upload input loads it with no page errors. Two specs, both proved to bite: the loader retries after a rejected load (fails without the cache clear), and parseExcelSheetNames rejects when the import does (fails with a timeout if the rejection is swallowed).
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).