Skip to content

Feature/v1.3.0: Trust procedural control flow #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ikelaiah merged 3 commits into from
Aug 6, 2026
Merged

Feature/v1.3.0: Trust procedural control flow #3

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
32b68e5
feat(v1.3.0): trust procedural control flow — mixed IF/WHILE
ikelaiah Aug 5, 2026
5938194
docs(v1.3.0): add user-facing release summary
ikelaiah Aug 5, 2026
ea32cae
feat(v1.3.0): complete procedural control flow (Workstream B)
ikelaiah Aug 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
61 changes: 37 additions & 24 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,8 @@ The application runs entirely in a browser and works from the local filesystem.
For the first stable release, see
[RELEASE_NOTE_v1.0.0.md](docs/RELEASE_NOTE_v1.0.0.md). For the v1.1.0 release, see
[RELEASE_NOTE_1.1.0.md](docs/RELEASE_NOTE_1.1.0.md). For the v1.2.0 release, see
[RELEASE_NOTE_1.2.0.md](docs/RELEASE_NOTE_1.2.0.md).
[RELEASE_NOTE_1.2.0.md](docs/RELEASE_NOTE_1.2.0.md). For the v1.3.0 release, see
[RELEASE_NOTE_1.3.0.md](docs/RELEASE_NOTE_1.3.0.md).

## Start here

Expand All @@ -61,7 +62,7 @@ For the first stable release, see

## 60-second quick start

1. Download the `v1.2.0` archive from
1. Download the `v1.3.0` archive from
[GitHub Releases](https://github.com/ikelaiah/ProcFlow/releases) or clone
this repository.
2. Extract the complete archive. Keep `index.html`, `styles.css`, `dist/`, and
Expand Down Expand Up @@ -128,14 +129,17 @@ statements.
analysis to another engineer.

ProcFlow imports SQL text, not report-definition files. SSRS/RDL import is on
the roadmap; for v1.2.0, paste or export the dataset SQL itself.
the roadmap; for v1.3.0, paste or export the dataset SQL itself.

## What ProcFlow can show

### Internal control flow

- `IF`, `ELSE`, and `CASE` decisions
- loops, loop exits, and early returns
- labelled loop-control and `GOTO`, with source span selection and explicit
"Unresolved label" nodes for missing targets
- cursor operations and the query behind a cursor
- statements and result sets
- procedure and function calls
- table reads and writes
Expand Down Expand Up @@ -186,7 +190,7 @@ than silently disappearing from the diagram.

## Supported SQL

ProcFlow v1.2.0 recognises:
ProcFlow v1.3.0 recognises:

- Microsoft T-SQL
- IBM DB2 SQL PL
Expand All @@ -197,16 +201,22 @@ Supported inputs include procedures, functions, triggers, views, plain SQL
statements, report dataset queries, and multi-object scripts where those object
types apply to the selected dialect.

Dialect-specific v1.2.0 coverage includes:

- **T-SQL:** semicolon-free statements with grammar-driven boundaries, `TRY`/
`CATCH`, `THROW`, `RAISERROR` severity, `XACT_STATE()`,
`@@TRANCOUNT`, nested transaction depth, savepoints, `SET XACT_ABORT`, and
invalid transaction-action termination.
- **DB2 SQL PL:** scoped handlers, cursors, `NOT FOUND` flow, and labelled loop
control.
Dialect-specific v1.3.0 coverage includes:

- **T-SQL:** mixed one-line and block `IF`/`WHILE` control flow (single
statement and `BEGIN`/`END` bodies in one AST), labelled `GOTO` and labels
with source spans plus a `goto_unresolved` diagnostic and explicit
"Unresolved label" node, cursor queries (`DECLARE … CURSOR FOR`) in the query
graph, concise `GRANT`/`WAITFOR`/`KILL`/cursor-operation labels, semicolon-free
statements with grammar-driven boundaries, `TRY`/`CATCH`, `THROW`,
`RAISERROR` severity, `XACT_STATE()`, `@@TRANCOUNT`, nested transaction depth,
savepoints, `SET XACT_ABORT`, and invalid transaction-action termination.
- **DB2 SQL PL:** mixed `THEN` and `BEGIN`/`END` `IF` forms, `BEGIN ATOMIC`
rollback scope, labelled loop control and `LEAVE`/`ITERATE` target validation,
`FOR … CURSOR FOR` queries in the query graph, scoped handlers, and
`NOT FOUND` flow.
- **PL/pgSQL:** `EXCEPTION` condition matching, transactional exception scopes,
and rethrow propagation.
rethrow propagation, and labelled loop-control target validation.
- **SQLite:** trigger `RAISE` actions, termination behavior, trigger `WHEN`,
conditional `WHERE`, and searched `CASE` paths.

Expand Down Expand Up @@ -246,7 +256,7 @@ endorsed by draw.io.

### Quick answers

| Question | ProcFlow v1.2.0 behavior |
| Question | ProcFlow v1.3.0 behavior |
|---|---|
| Is SQL uploaded? | No. Analysis and rendering happen in the browser tab. |
| Does it connect to a database? | No. There is no driver, connection string, or query execution. |
Expand Down Expand Up @@ -280,7 +290,7 @@ network-submission code. The only bundled third-party runtime is the pinned
Mermaid 10.9.1 renderer. Its MIT licence is stored at
`vendor/mermaid/LICENSE`.

The SHA-256 of `vendor/mermaid/mermaid.min.js` in v1.2.0 is:
The SHA-256 of `vendor/mermaid/mermaid.min.js` in v1.3.0 is:

```text
61B335A46DF05A7CE1C98378F60E5F3E77A7FB608A1056997E8A649304A936D6
Expand All @@ -291,7 +301,7 @@ so the release checksum remains reproducible across operating systems.

### Guidance for security review

1. Review and pin the `v1.2.0` tag or its exact commit.
1. Review and pin the `v1.3.0` tag or its exact commit.
2. Verify the vendored Mermaid checksum.
3. Review the runtime files listed above.
4. Open the reviewed files locally or serve them from an approved internal
Expand Down Expand Up @@ -330,7 +340,7 @@ and contains no automatic data-submission path.
be detected.
- Temporary-table, synonym, linked-server, and cross-database resolution is
lightweight.
- SSRS/RDL files are not imported in v1.2.0.
- SSRS/RDL files are not imported in v1.3.0.
- Large draw.io exports can require manual rearrangement.

Always confirm critical dependencies, execution paths, transaction behavior,
Expand Down Expand Up @@ -396,9 +406,9 @@ Then open:
- `http://127.0.0.1:8000/tests/ui.html` — browser interaction and local-runtime
tests

The v1.2.0 baseline is:
The v1.3.0 baseline is:

- 156 golden and boundary assertions
- 181 golden and boundary assertions
- 400 deterministic mutation cases
- 13 browser interaction tests

Expand Down Expand Up @@ -426,11 +436,14 @@ assets/
docs/
├── PR_NOTE_1.1.0.md
├── PR_NOTE_1.2.0.md
├── PR_NOTE_1.3.0.md
├── RELEASE_NOTE_1.1.0.md
├── RELEASE_NOTE_1.2.0.md
├── RELEASE_NOTE_1.3.0.md
├── RELEASE_NOTE_v1.0.0.md
├── RELEASE_NOTE_v1.1.0.md
└── RELEASE_NOTE_v1.2.0.md
├── RELEASE_NOTE_v1.2.0.md
└── RELEASE_NOTE_v1.3.0.md
scripts/
└── file-smoke.mjs # dependency-free local-file release smoke test
src/
Expand Down Expand Up @@ -487,12 +500,12 @@ Then verify:
2. `git status --short` shows only the intended release changes.
3. Generated `dist/` files match their TypeScript sources.
4. The Mermaid SHA-256 matches the value in this README and the workflow.
5. `RELEASE_NOTE_1.2.0.md` matches the final tag contents.
5. `RELEASE_NOTE_1.3.0.md` matches the final tag contents.
6. The complete archive opens locally with `index.html`.
7. The tag is named `v1.2.0`.
7. The tag is named `v1.3.0`.

The release can then be created manually from the `v1.2.0` tag using
[RELEASE_NOTE_1.2.0.md](docs/RELEASE_NOTE_1.2.0.md).
The release can then be created manually from the `v1.3.0` tag using
[RELEASE_NOTE_1.3.0.md](docs/RELEASE_NOTE_1.3.0.md).

## Roadmap after v1.0.0

Expand Down
32 changes: 23 additions & 9 deletions dist/src/dialects.js
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion dist/src/dialects.js.map
View file
Open in desktop

Large diffs are not rendered by default.

Loading
Loading