dc
fb02788caf
Two callers disagreed about who sets a library's expanded flag, and the code
that focuses the tables search box depended on an id that only exists while the
library is open.
selectTable ended by toggling the flag:
library['expanded'] ? (library['expanded'] = false) : (library['expanded'] = true)
That was written against Clarity's two-way binding, where the caret also
toggled the same value, so the two cancelled out in the case anyone noticed.
libraryOnClick already toggles it for a user click, and loading a library's
tables means the library is open, so selectTable now sets it to true and leaves
the toggle to the handler.
The search box was found with document.querySelector('#search_<ref>'), which
works only while the node is expanded and re-rendered. It is now a
@ViewChildren lookup matched on data-libref, so nothing depends on that id -
which is also one less assumption for the tree work in #554, where the markup
that writes the id is due to change.
No behaviour change intended: with Clarity still rendering the tree, the five
specs that exercise it are 30/31, the single failure being viewbox test 7, the
animated-expansion flake that #554 owns. viewer-labels 5/5, full-table-search
1/1, download 8/8, row-cell-limits 5/5. Unit suite 1401 passing.
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).