Skip to content
Permalink
Browse files
renamed all instances of mock to daffodil - keeping case (#4)
Co-authored-by: Shane Dell <dells@ctc.com>
  • Loading branch information
Shanedell and dells-ctc committed May 25, 2021
1 parent 8778f5d commit 383fd4882a8fe51adf21b5ae31fe252056800447
Showing 12 changed files with 109 additions and 220 deletions.
@@ -3,7 +3,7 @@ dist
node_modules
.vscode-test/
npm-debug.log
mock-debug.txt
daffodil-debug.txt
*.vsix
.DS_Store
daffodil-debugger*
@@ -1,113 +1,2 @@
## 0.45.7
* Add support for data breakpoint access types (a big _Thank You_ to @yannickowow for the PR)

## 0.45.6
* Add support for a custom inline value provider that matches variables in a case-insensitive way.
* Group "run" and "debug" editor commands in the new "run" submenu

## 0.45.5
* Provide help texts for exception filters via DAP's new `description` and `conditionDescription`properties.

## 0.45.4
* Add support for the `exceptionInfo` request.

## 0.45.3
* Add support for exception filters (and conditions). "Named Exception" will break on the `exception(xxx)` pattern if the exception condition is set to `xxx`. "Other Exceptions" will break on the word `exception` and the `exception(...)` patterns not matched by "Named Exception".

## 0.44.0
* Emit "Invalidated" event if client supports it.
* Changed context menu action "Show as Hex" to "Toggle between decimal and heximal formatting"

## 0.43.0
* Add context menu action "Show as Hex" to integer variables in Variables view
* Add new run option "namedPipeServer" for debug adapter in extension.ts
* Use new extension API for passing the "noDebug" option to "vscode.debug.startDebugging"
* Support to run Mock Debug in the browser/web worker

## 0.42.2
* Project hygiene: get rid of all warnings
* use eslint instead of tslint
* align with latest yeoman generator for VS Code

## 0.42.1
* Add "run" and "debug" actions to editor title
* Implement "Run without debugging"

## 0.41.0
* Add support for StepIn and StepOut: StepIn moves execution one character to the right, StepIn to the left
* Add support for StepInTargets: every word in the stopped line is considered one stack frame; StepInTargets returns targets for every character of the stack frame with the given frameId.

## 0.40.0
* Exercise new dynamic debug config API.

## 0.39.0
* Exercise progress events: typing "progress" in the REPL starts a sequence of (cancellable) progress events if the clients supports this via the `supportsProgressReporting` client capability.
* Exersise new completion item attributes `selectionStart` and `selectionLength`: "array[]" moves cursor between the brackets and "func(arg)" selects "arg".

## 0.38.0
* Exercise the new group feature of output events: 'log(start)' or 'log(startCollapsed)' starts a group, 'log(end)' ends a group.

## 0.37.0
* Add a simple vscode.EvaluatableExpressionProvider to show how to control what gets shown in a debug hover.

## 0.36.0
* Extend the run mode by an 'inline' run mode (in addition to 'external' and 'server').

## 0.35.0
* Support the 'breakpointLocations' request.
* Make 'variables' request cancelable.

## 0.34.0
* Add support for persisted data breakpoints.

## 0.33.0
* Add support for (sorted) REPL completions.

## 0.32.0
* Add support for data breakpoints.

## 0.31.0
* Added code to show how to control what debug executable is used.

## 0.30.0
* Updated dependencies.

## 0.29.0
* Move off proposed API for the EMBED_DEBUG_ADAPTER mode: embedded debug adapter now uses vscode.DebugAdapterDescriptorFactory.

## 0.28.0
* Update dependencies.

## 0.27.0
* Update dependencies.

## 0.26.0
* Improved the launch configuration snippet and added a `"stopOnEntry": true`.

## 0.25.0
* Added the `"multi-root ready"` keyword.

## 0.24.0
* Add support for starting a debug session without a launch configuration.
* Require 1.17 version of VS Code.

## 0.23.0
* Added supported for creating and deleting breakpoints from the REPL. Use `new 123` to create a breakpoint in line 123, and `del 123` to delete it.
* Use 1.24.0 version of Debug Adapter Protocol and libraries.

## 0.22.0
* Refactored the 'Mock Debugger' functionality into a separate class. This makes it more obvious how a debug adapter 'adapts' to a debugger or runtime.

## 0.21.0
* Shows the source location of log output. A `log(any text)` in the input sends the text in parenthesis to the debug console.

## 0.20.0
* Use 1.23.0 version of Debug Adapter Protocol and libraries.

## 0.19.0
* Add tslint
* Use 1.19.0 version of Debug Adapter Protocol and libraries.

## 0.18.2
* Added 'trace' attribute to launch configuration: set it to 'true' to enable logging of the Debug Adapter Protocol.

## 0.0.1
* Create vscode extension for debugging daffodil schemas
@@ -65,11 +65,11 @@
"main": "./dist/ext/extension.js",
"browser": "./dist/web/extension.js",
"activationEvents": [
"onDebugResolve:mock",
"onDebugDynamicConfigurations:mock",
"onCommand:extension.mock-debug.getProgramName",
"onCommand:extension.mock-debug.runEditorContents",
"onCommand:extension.mock-debug.debugEditorContents"
"onDebugResolve:daffodil",
"onDebugDynamicConfigurations:daffodil",
"onCommand:extension.daffodil-debug.getProgramName",
"onCommand:extension.daffodil-debug.runEditorContents",
"onCommand:extension.daffodil-debug.debugEditorContents"
],
"workspaceTrust": {
"request": "never"
@@ -78,48 +78,48 @@
"menus": {
"editor/title/run": [
{
"command": "extension.mock-debug.runEditorContents",
"command": "extension.daffodil-debug.runEditorContents",
"when": "resourceLangId == markdown"
},
{
"command": "extension.mock-debug.debugEditorContents",
"command": "extension.daffodil-debug.debugEditorContents",
"when": "resourceLangId == markdown"
}
],
"commandPalette": [
{
"command": "extension.mock-debug.debugEditorContents",
"command": "extension.daffodil-debug.debugEditorContents",
"when": "resourceLangId == markdown"
},
{
"command": "extension.mock-debug.runEditorContents",
"command": "extension.daffodil-debug.runEditorContents",
"when": "resourceLangId == markdown"
}
],
"debug/variables/context": [
{
"command": "extension.mock-debug.toggleFormatting",
"when": "debugType == 'mock' && debugProtocolVariableMenuContext == 'simple'"
"command": "extension.daffodil-debug.toggleFormatting",
"when": "debugType == 'daffodil' && debugProtocolVariableMenuContext == 'simple'"
}
]
},
"commands": [
{
"command": "extension.mock-debug.debugEditorContents",
"command": "extension.daffodil-debug.debugEditorContents",
"title": "Debug File",
"category": "Mock Debug",
"category": "Daffodil Debug",
"enablement": "!inDebugMode",
"icon": "$(debug-alt)"
},
{
"command": "extension.mock-debug.runEditorContents",
"command": "extension.daffodil-debug.runEditorContents",
"title": "Run File",
"category": "Mock Debug",
"category": "Daffodil Debug",
"enablement": "!inDebugMode",
"icon": "$(play)"
},
{
"command": "extension.mock-debug.toggleFormatting",
"command": "extension.daffodil-debug.toggleFormatting",
"title": "Toggle between decimal and hex formatting"
}
],
@@ -130,11 +130,11 @@
],
"debuggers": [
{
"type": "mock",
"type": "daffodil",
"languages": [
"markdown"
],
"label": "Mock Debug",
"label": "Daffodil Debug",
"program": "./out/daffodilDebugger.js",
"runtime": "node",
"configurationAttributes": {
@@ -169,7 +169,7 @@
},
"initialConfigurations": [
{
"type": "mock",
"type": "daffodil",
"request": "launch",
"name": "Ask for file name",
"program": "${workspaceFolder}/${command:AskForProgramName}",
@@ -178,10 +178,10 @@
],
"configurationSnippets": [
{
"label": "Mock Debug: Launch",
"label": "Daffodil Debug: Launch",
"description": "A new configuration for 'debugging' a user selected markdown file.",
"body": {
"type": "mock",
"type": "daffodil",
"request": "launch",
"name": "Ask for file name",
"program": "^\"\\${workspaceFolder}/\\${command:AskForProgramName}\"",
@@ -190,7 +190,7 @@
}
],
"variables": {
"AskForProgramName": "extension.mock-debug.getProgramName"
"AskForProgramName": "extension.daffodil-debug.getProgramName"
}
}
]
@@ -1,8 +1,8 @@
# VS Code Mock Debug
# VS Code Daffodil Debug

This is a starter sample for developing VS Code debug adapters.

**Mock Debug** simulates a debug adapter for Visual Studio Code.
**Daffodil Debug** simulates a debug adapter for Visual Studio Code.
It supports *step*, *continue*, *breakpoints*, *exceptions*, and
*variable access* but it is not connected to any real debugger.

@@ -12,28 +12,28 @@ adapter for VS Code. It can be used as a starting point for developing a real ad
More information about how to develop a new debug adapter can be found
[here](https://code.visualstudio.com/docs/extensions/example-debuggers).

## Using Mock Debug
## Using Daffodil Debug

* Install the **Mock Debug** extension in VS Code.
* Install the **Daffodil Debug** extension in VS Code.
* Create a new 'program' file `readme.md` and enter several lines of arbitrary text.
* Switch to the debug viewlet and press the gear dropdown.
* Select the debug environment "Mock Debug".
* Select the debug environment "Daffodil Debug".
* Press the green 'play' button to start debugging.

You can now 'step through' the `readme.md` file, set and hit breakpoints, and run into exceptions (if the word exception appears in a line).

![Mock Debug](images/mock-debug.gif)
![Daffodil Debug](images/daffodil-debug.gif)

## Build and Run

[![build status](https://travis-ci.org/Microsoft/vscode-mock-debug.svg?branch=master)](https://travis-ci.org/Microsoft/vscode-mock-debug)
[![build status](https://ci.appveyor.com/api/projects/status/empmw5q1tk6h1fly/branch/master?svg=true)](https://ci.appveyor.com/project/weinand/vscode-mock-debug)
[![build status](https://travis-ci.org/Microsoft/vscode-daffodil-debug.svg?branch=master)](https://travis-ci.org/Microsoft/vscode-daffodil-debug)
[![build status](https://ci.appveyor.com/api/projects/status/empmw5q1tk6h1fly/branch/master?svg=true)](https://ci.appveyor.com/project/weinand/vscode-daffodil-debug)


* Clone the project [https://github.com/Microsoft/vscode-mock-debug.git](https://github.com/Microsoft/vscode-mock-debug.git)
* Clone the project [https://github.com/Microsoft/vscode-daffodil-debug.git](https://github.com/Microsoft/vscode-daffodil-debug.git)
* Open the project folder in VS Code.
* Press `F5` to build and launch Mock Debug in another VS Code window. In that window:
* Press `F5` to build and launch Daffodil Debug in another VS Code window. In that window:
* Open a new workspace, create a new 'program' file `readme.md` and enter several lines of arbitrary text.
* Switch to the debug viewlet and press the gear dropdown.
* Select the debug environment "Mock Debug".
* Select the debug environment "Daffodil Debug".
* Press `F5` to start debugging.
@@ -5,7 +5,7 @@
"version": "0.2.0",
"configurations": [
{
"type": "mock",
"type": "daffodil",
"request": "launch",
"name": "Debug test.md",
"program": "${workspaceFolder}/jpeg.dfdl.xsd",
@@ -1,11 +1,11 @@
# VS Code Mock Debug
# VS Code Daffodil Debug

Mock Debug local_i allows to "debug" markdown files (like this).
Daffodil Debug local_i allows to "debug" markdown files (like this).
The text of the markdown is considered the "program to debug" and certain keywords trigger specific functionality:

* if debugging stops on a line, the line becomes a stack in the CALL STACK with the words shown as frames.
Here is a long stack trace: a b c d e f g h i j k l m n o p q r s t u v w x y z a b c d e f g h i j k l m n o p q r s t u v w x y z a b c d e f g h i j k l m n o p q r s t u v w x y z.
* Variables are just synthesized by Mock Debug, they do not originate from the markdown file.
* Variables are just synthesized by Daffodil Debug, they do not originate from the markdown file.

## Inline Values

@@ -16,8 +16,8 @@ And these with different casing: Local_I, LOCAL_S

## Breakpoints:

Breakpoints can be set in the breakpoint gutter of the editor (even before a Mock Debug session was started).
If a Mock Debug session is active, breakpoints are "validated" according these rules:
Breakpoints can be set in the breakpoint gutter of the editor (even before a Daffodil Debug session was started).
If a Daffodil Debug session is active, breakpoints are "validated" according these rules:

* if a line is empty or starts with `+` we don't allow to set a breakpoint but move the breakpoint down
* if a line starts with `-` we don't allow to set a breakpoint but move the breakpoint up

0 comments on commit 383fd48

Please sign in to comment.