What's new

0.2.7

• Website: datastep-studio.pages.dev with Get started, the user manual, the how-to guide, the release notes and the videos; linked from the Marketplace page and the extension's details.
• The manual has a What's new section.

0.2.6

• Format SAS Program (right-click; also Format Document / Format Selection) (Community): keywords upper, names lower, 2 spaces per level, = and IF / ELSE aligned, long macro calls comma first, long PROC SQL statements one clause per line, short PROC SORT on one line, &var. periods. Macro text, strings, comments, DATALINES, the header and your line breaks stay; a token comparison proves that only the layout changed. Only when asked.
• Style hints in Problems: * comments, unsplit ERROR: / WARNING:, Boolean flags, macro variables without a period.
• Fixed: removing breakpoints while the DATA step debugger finished could leave a debugger command in SAS; the next statement then failed with "Statement is not valid". Debugger commands now go one at a time, and nothing after QUIT.

0.2.5

• Fixed: the DATA step debugger waits until a query of a view still running in SAS is done before it starts (they could mix, and the next statement then failed with "Statement is not valid").
• Debug Macro on a call: with the cursor on a call in a program, the definition is found (in the %INCLUDEd files, the folder, the macros folders), and the call pane holds the call as written.
• Debug DATA Step on a step that calls a macro: the step is expanded beside the program (the macro's statements written out) and the debugger steps through it; a breakpoint with a condition such as midtc = "2024-12" stops at that observation. The expansion only compiles the step; it reads and writes no data.
• Fixed: a data set without variables shows a clear message instead of "could not read the SAS result".
• Fixed: while the macro debugger is paused, Libraries lists the data sets the macro has made so far (it said "SAS is busy"); a double-click opens them. It refreshes when the macro rests a moment, so stepping stays fast.

0.2.4

• Watch the Installation Video: every step from installing to the first run and both debuggers, also in Get Started.
• The manual says what VS Code asks on the first install (trust the publisher DataStep Labs).

0.2.3

• Fixed: a new SAS Server window that VS Code did not trust yet (Restricted Mode) showed a "!" on its folder and no DataStep Studio commands. DataStep Studio now works in Restricted Mode and asks once for trust, for the debuggers.
• Fixed: while the macro debugger is paused, a data set the macro created opens in the data viewer (the query runs inside the paused macro, which sees its WORK library).
• The guide programs are no longer part of the extension.

0.2.2

• Help on the Marketplace page: manual, videos, questions, the SAS Community thread, Report a Problem.
• Send Feedback offers the SAS Community thread.
• An empty window's Explorer has an Open SAS Server Folder button.

0.2.1

• The user manual and the how-to guide are on the Marketplace page, below the overview.

0.2.0

• Run in Batch (Community): right-click programs or a folder in the Explorer. Each program runs in a new SAS session, one after another; program.log and program.lst are written next to it, errors appear in Problems, and a summary shows how the batch went. Your own SAS session stays free.
• Open Manual and Open How-To Guide: the manual and the how-to guide ship with the extension.

0.1.1

• Videos inside VS Code: Watch the 2-Minute Tour and Watch the Macro Debugger Video.
• Get Started shows pictures of every step.
• Guide example 5 and the manual's macro debugger chapter use a new example: %sum_of_squares calls %square.

0.1.0 (Community Early Access)

First public version: run modes, SAS Log and Suspicious Log, data viewer, Libraries, Variables and Options, SAS Server window and project sync, autocomplete with SAS 9.4 documentation, smart code, DATA step and macro debuggers, connection profiles with the password in the system keychain, Check Setup, Send Feedback.