dc
7da67eb17b
Rung 4 of the #376 ratchet. It clears the last 5 findings and promotes the three rules that produced them to "error": minMacroNameLength, lowerCaseMacroNames and indentationMultiple. `sasjs lint` now reports no warnings and no errors across the project. - viewdata.sas wraps its service body in a helper macro named `x`; it becomes viewdata_body. The wrapper is what keeps the %global and the %return in one macro scope. - usergroupsbymember.sas (sas9) builds work.iwant inside a helper macro named `x`; it becomes build_iwant. - refreshtablelineage.sas (sas9) defines `getTables` with uppercase; it becomes `gettables`, at the definition, the %mend and its seven calls. - getstagetable.test.sas: one comment line carried three leading spaces where the file uses two. VERIFICATION - `npm run lint:sas`: 0 warnings, 0 errors, exit 0, "All matched files use @sasjs/lint code style!". - `sasjs compile`: succeeds. - Deployed to sas.4gl.io and ran the SAS suite there against a scratch appLoc (/Public/app/dc-lint-ratchet) seeded with makedata: "Tests that pass: 64/64 (100%)". The viewdata and usergroupsbymember suites are in that run, so the two renames are covered by passing tests.
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).