work.browser_url_vars is filled from the page URL, and on SAS 9 and Viya the page URL is the platform's own job URL. So the table carries the platform's parameters (_FILE, _program, _debug, _webout) as well as Data Controller's (embed, labels). The page said only that the parameters are DC's, which invites a hook author to read _FILE as a DC parameter.
One paragraph added to the browser_url_vars section; no other change.
Follow-up to #9, from the review of dc/dc#326.
`work.browser_url_vars` is filled from the page URL, and on SAS 9 and Viya the page URL is the platform's own job URL. So the table carries the platform's parameters (`_FILE`, `_program`, `_debug`, `_webout`) as well as Data Controller's (`embed`, `labels`). The page said only that the parameters are DC's, which invites a hook author to read `_FILE` as a DC parameter.
One paragraph added to the `browser_url_vars` section; no other change.
On SAS 9 and Viya the app is reached through the platform's job URL, so
work.browser_url_vars carries the platform's parameters (_FILE, _program,
_debug, _webout) alongside DC's. Say so, so a hook author does not read
_FILE as a Data Controller parameter.
allan
merged commit 19e50fdf6a into main2026-09-28 00:17:28 +00:00
allan
deleted branch docs/platform-params2026-09-28 00:17:28 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Follow-up to #9, from the review of dc/dc#326.
work.browser_url_varsis filled from the page URL, and on SAS 9 and Viya the page URL is the platform's own job URL. So the table carries the platform's parameters (_FILE,_program,_debug,_webout) as well as Data Controller's (embed,labels). The page said only that the parameters are DC's, which invites a hook author to read_FILEas a DC parameter.One paragraph added to the
browser_url_varssection; no other change.