debugger/src/main/scala/org.apache.daffodil.debugger.dap/DAPodil.scala (7 lines): - line 149: * TODO: rename extractor - line 164: // TODO: java-debug doesn't seem to support the Restart request - line 210: // TODO: ensure `launch` is atomic - line 532: // TODO: extract "control" interface from "state" interface - line 671: copy(stack = stack.pop) // TODO: warn of bad pop - line 755: // TODO: path *can* be optional for non-empty source reference ids; need to experiment - line 780: * TODO: VS Code doesn't seem to notice supportsRestartRequest=true and sends Disconnect (+restart) requests instead src/language/semantics/xslLexer.ts (6 lines): - line 308: // TODO: Handle internal DTD subset - line 365: // TODO: ]] not permited on its own in CDATA, show error - line 375: // TODO: check first char of element name is oK - line 426: // TODO: force error - guessing intended end of start tag - line 538: // TODO: check next char is not ';' - line 625: // TODO: check next char is not ';' debugger/src/main/scala/org.apache.daffodil.debugger.dap/Parse.scala (5 lines): - line 648: ) // TODO: it's a bit incongruous to have a separate channel for infoset changes, vs. streaming Parse.Event values - line 747: // TODO: when Parse.Exception has source coordinates, include it into a more structured OutputEvent - line 875: // TODO: Get better values than toString() when https://issues.apache.org/jira/browse/DAFFODIL-1200 is completed. - line 923: .groupBy(_.namespace) // TODO: handle NoNamespace or UnspecifiedNamespace as top-level? - line 1268: // TODO: there's a race between the readers of `events` and `state`, so somebody could react to a hit breakpoint before the event data was committed src/language/semantics/xsltTokenDiagnostics.ts (4 lines): - line 188: // TODO: when within literal result element, iterate up stack until we get to an XSLT instruction: - line 227: // TODO: for attributes on non-xsl instructions, check that name is in the attributeGroup: xsl:literal-result-element-attributes (e.g. xsl:expand-text) - line 948: // TODO: check arity of variables of type 'function' - line 1113: // TODO: check arity of variable of type 'function' debugger/src/main/scala/org.apache.daffodil.debugger.dap/Next.scala (1 line): - line 31: // TODO: optional starting value src/dataEditor/dataEditorClient.ts (1 line): - line 89: const MAX_LOG_FILES: number = 5 // Maximum number of log files to keep TODO: make this configurable src/language/semantics/xpLexer.ts (1 line): - line 1258: // TODO: check if value equals xs:integer or element? src/svelte/src/stores/index.ts (1 line): - line 196: // TODO: I think there is a cleaner way to do this given that we already have the encoded data in the respective viewports