dc
c8c0858295
sas/.sasjslint now promotes noUnusedMacros to "error", so the rule fails
the build rather than printing a warning. The 54 findings it reported are
gone:
- 46 header entries nothing calls are dropped. Each removal was checked
against the compiled artefacts rather than the linter alone: the
project was compiled before and after, and the two sasjsbuild trees
compared. 37 macro definitions disappear from the generated programs -
every one of them either a duplicate of a definition the file still
reaches through another declared macro, or a macro no generated program
calls. No macro that a generated program calls lost its definition.
- 8 entries are kept, in five files that carry
@sasjslint {"noUnusedMacros": false} with the reason written above it:
the three serviceInit programs and serviceterm.sas declare mpeinit and
mpeterm without calling them, because that declaration is how a service
body reaches those macros at all; loadfile.sas declares mp_binarycopy
for the fallback that is commented out on SAS 9.4 and later.
- Four headers are left with no macros to declare, so their empty
<h4> SAS Macros </h4> section is removed rather than kept as a stub.
@sasjs/cli is bumped 6.2.0 -> 6.5.0 in sas/package.json. The lint engine
ships inside the CLI and is not a direct dependency, so the pinned CLI is
what fixes the rule set: 6.2.0 resolves @sasjs/lint 4.3.0, 6.5.0 pins
4.9.0 exactly. Both versions were compiled against this tree and the
sasjsbuild output is byte-identical, so the bump changes the lint engine
and nothing else.
`sasjs lint` is also now reachable as `npm run lint:sas`, and a CI step in
build.yaml runs it. Until now nothing ran SAS lint automatically, and a
bare `sasjs` resolves whatever CLI is installed globally - a different
lint version reports a different rule set, which is why the counts in
issue #376 (taken with 6.2.5) do not match the pinned 6.2.0.
43 warnings remain under the rules not yet promoted: noUndeclaredMacros
(25), noBannedStrings (13), macro name length and case (4),
indentationMultiple (1). They are the next rungs of the ratchet.
The pre-commit Prettier gate could not run: it needs client/node_modules,
which this worktree does not install, and the fix it attempted touched
three client files that this change does not modify (reverted). No client
file is in this commit.
44 lines
3.0 KiB
JSON
44 lines
3.0 KiB
JSON
{
|
|
"name": "dc-sas",
|
|
"description": "dc-sas",
|
|
"scripts": {
|
|
"cpfavicon": "cp sasjs/utils/favicon.ico ../client/dist/favicon.ico",
|
|
"lint:sas": "sasjs lint",
|
|
"build": "cd ../client && npm run build",
|
|
"deploy:server": "rsync -avhe ssh ../client/dist/* --delete allbow@sas.4gl.io:/opt/sas/sas9/config/Lev1/Web/WebServer/htdocs/allbow/server",
|
|
"sas9": "rsync -avhe ssh ./dist/* --delete ${npm_config_account}@sas.4gl.io:/opt/sas/sas9/config/Lev1/Web/WebServer/htdocs/${npm_config_account}/dc",
|
|
"sas9cbd": "npm run sas9a && npm run sas9b && npm run sas9c && npm run sas9d && npm run sas9e && npm run sas9f && npm run sas9g",
|
|
"sas9a": "./sasjs/utils/delete_metafolder.sh",
|
|
"sas9b": "sasjs cbd -t sas9",
|
|
"sas9c": "sasjs request services/admin/buildtermsas9 -t sas9 ",
|
|
"sas9d": "./sasjs/utils/export_spk.sh",
|
|
"sas9e": "sasjs request services/admin/makedata -d deploy/makeDataSas9.json -t sas9 ",
|
|
"sas9f": "sasjs request services/admin/refreshtablelineage -t sas9 ",
|
|
"sas9g": "sasjs request services/admin/refreshcatalog -t sas9",
|
|
"4gl": "npm run cpfavicon && sasjs cbd -t 4gl && npm run 4glmakedata",
|
|
"4glmakedata": "sasjs request services/admin/makedata -d deploy/makeData4GL.json -l sasjsresults/makedata_4gl.log -o sasjsresults/makedata_4gl.json -t 4gl",
|
|
"server": "npm run cpfavicon && sasjs cbd -t server && npm run serverdata",
|
|
"server-mihajlo": "npm run cpfavicon && sasjs cbd -t server-mihajlo && npm run serverdata-mihajlo",
|
|
"serverdata-mihajlo": "sasjs request services/admin/makedata -d deploy/makeDataServer.json -l sasjsresults/makedata_server.log -o sasjsresults/makedata_server.json -t server-mihajlo",
|
|
"serverdata": "sasjs request services/admin/makedata -d deploy/makeDataServer.json -l sasjsresults/makedata_server.log -o sasjsresults/makedata_server.json -t server",
|
|
"nextviya": "sasjs cb -t nextviya && sasjs run sasjsbuild/viya.sas -t nextviya",
|
|
"nextviyamakedata": "sasjs request services/admin/makedata -d deploy/makeDataNextViya.json -c deploy/configNextViya.json -l sasjsresults/makedata_nextviya.log -o sasjsresults/makedata_nextviya.json -t nextviya",
|
|
"viya": "npm run viyacbd && sasjs test",
|
|
"viyacbd": "sasjs folder delete /Public/app/viya && sasjs cbd -t viya && npm run viyadata",
|
|
"viyadata": "sasjs request services/admin/makedata -d deploy/makeDataViya.json -l sasjsresults/makedata.log -o sasjsresults/output.json -t viya",
|
|
"v4data": "sasjs request services/admin/makedata -d deploy/makeDataV4.json -l sasjsresults/makedatav4.log -o sasjsresults/outputv4.json -t v4",
|
|
"sasdocs": "sasjs doc && ./sasjs/utils/deploydocs.sh",
|
|
"sas719setup": "sasjs cbd -t sas719 && npm run sas719data",
|
|
"sas719data": "sasjs request services/admin/makedata -d deploy/makeDataSas719.json -l sasjsresults/makedata_sas719.log -o sasjsresults/makedata_sas719.json -t sas719",
|
|
"sas719test": "sasjs test -t sas719"
|
|
},
|
|
"private": true,
|
|
"dependencies": {
|
|
"@sasjs/cli": "6.5.0",
|
|
"@sasjs/core": "7.0.3"
|
|
},
|
|
"overrides": {
|
|
"nanoid": "3.3.18"
|
|
}
|
|
}
|