6 Commits

Include renames

Author	SHA1	Message	Date
allan	ca62bb391c	Merge pull request 'docs(options): the EDIT limits truncate the grid and warn' (#22) from docs/editor-limit-warning into main ... Reviewed-on: #22	2026-10-26 11:59:54 +00:00
dc	c7626b2797	docs(developer): a page for the browser variables, and links from where they are used ... browser_info and browser_url_vars were only described inside the troubleshooting page, under Support Diagnostics. That is the right place to find them if you already know they exist and are looking for a log line; it is not where anyone looks when writing a hook, which is what they are mostly for. The new Developer Guide page carries the whole subject: which services receive the two tables, the column lists, the debug values per platform and the MPEINIT log lines, reading them from a hook with the exist() guard, and the reminder that they are client-supplied and so diagnostics rather than a security boundary. Troubleshooting keeps three stub headings - browser_info, browser_url_vars, reading-them-from-a-hook - pointing at the page, so the anchors that are already published keep resolving, and the detail is not maintained twice. Linked from the three places a hook author actually starts: the HOOK Scripts section of the MPE_TABLES page, the pre-edit hook guide (where the editor's inputs are listed), the two-rule-sets guide (post-edit hook), and the VA embed page, where embed=va is exactly the kind of thing a hook wants to branch on.	2026-10-26 11:42:35 +00:00
dc	561e92e090	docs(developer-guide): name both EDIT caps in the hook page ... The truncation is whichever of DC_MAXOBS_WEBEDIT and DC_MAXCELLS_WEBEDIT binds first, and for a wide table it is the cell cap - floor(cells/columns) rows, potentially far below the row limit. The hook page named only the row cap and quoted its 250 default, so a hook author would check the row count alone. Same correction in the two-rule-sets page.	2026-10-22 19:27:51 +00:00
dc	971b007606	docs(options): the EDIT limits truncate the grid and warn ... getdata no longer refuses a selection over DC_MAXOBS_WEBEDIT or DC_MAXCELLS_WEBEDIT - it serves the rows within the limit and flags the truncation against the table name. Update the option reference and the two developer-guide pages that claimed the edit screen stops with "Table is too big". The hook page also carried the old 500 row default.	2026-10-22 16:40:48 +00:00
dc	8a22e28a46	docs(developer-guide): correct the LIBREF/DS macro-scope note ... The post-edit hook section claimed a `%let` "creates a new variable in the hook's own scope and is silently discarded" while `call symputx` updates the existing one. That is not how SAS resolves it: LIBREF and DS already exist in an enclosing symbol table (mpe_loader's local table), and a macro only gets a new local when the name is absent from every enclosing table, so both forms assign to the same variable. Reworded to state that, and to keep the practical advice (call symputx is explicit and does not depend on the enclosing scope still holding the name). Raised in review of #16.	2026-10-15 18:28:36 +00:00
dc	cc91f8b1f9	docs(developer-guide): add a Developer Guide section ... Two pages, both aimed at SAS developers rather than end users: - Filter in a Pre-Edit Hook: what editors/getdata returns (sasparams.FILTER_TEXT and the query clauses, never FILTER_RK), when PRE_EDIT_HOOK runs relative to the filter, and a worked example that widens a date filter to the previous quarter - re-reading the table so the rows match, and keeping Row Level Security applied to both branches. - One Table, Two Rule Sets: moved from the datacontroller.io blog, so the developer-facing material lives in one place. Images moved to docs/img/.	2026-10-15 16:16:15 +00:00