dc
7d2cc846ff
The deploy screens asked for a physical folder the deployment user can write to, as a single text box, and found out whether it worked only by running the whole deployment. They now get a picker and a Validate button, backed by the makedata actions that already answer those two questions. A new app-dc-location component renders the path as an editable input - the picker is a convenience over it, never a replacement, because a folder the deployment user cannot open is not listed and a customer may want a path that does not exist yet. Browse lists one level at a time (ACTION=DIRLIST, DEPTH 1, MAXOBS 500), with Up, a "Use this folder" for where you are standing, and a per row Use. Validate calls ACTION=WRITECHECK and reports the verdict inline - writeable, or the reason it is not - instead of leaving it to the deployment to fail. Both screens use it: the Viya setup screen (which runs makedata through the adapter) and the Sasjs configurator (which opens makedata as a URL). The mkdata calls now send ACTION=MAKEDATA, since the service requires it. Details worth knowing: - every value read from the service is trimmed: SAS has no zero length character value, so a blank field arrives as a single space and reads as a value to any `||` or `@if`. - the listing's level 0 row is the folder being listed, not a folder to drill into - except when the parent is blank, where the level 0 rows are the platform roots. - failures are shown inline rather than as abort modals: the two requests pass suppressErrorAbortModal/suppressSuccessAbortModal, because a refused path is an expected answer here, not a crash. - parentOf handles a drive root (C:\) and a unix root without inventing an empty path. Frontend tests: 14 new specs (38 in the deploy folder, all passing), including a template spec for the browser panel and one for the verdict line, both mutation checked.