Skip to content

Commit

Permalink
add changelog, prepare v7.0.0
Browse files Browse the repository at this point in the history
  • Loading branch information
badetitou committed Jan 27, 2021
1 parent 445469a commit 7f581f3
Show file tree
Hide file tree
Showing 2 changed files with 51 additions and 1 deletion.
50 changes: 50 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,50 @@
# Changelog

## v0.0.7

This update comes from the release of the [Pharo-LanguageServer](https://github.com/badetitou/Pharo-LanguageServer).
Thus, most of the code modification can be found in the server repository.

### Users

#### DAP

- Can stepIn (into), step next (through), step out (over)
- Can access the source code of the stack element
- Show the line where the error was signaled

#### LSP

- Add the help signature feature
- When writing a method, a help box appears with information for this methods (parameters, comment, *etc.*)

### Developers

#### DAP

- The server uses now a Debug Session
- The DAP gives correctly the socket port using LSP

## v0.0.6

### Users

#### DAP

We introduce the [DAP](https://microsoft.github.io/debug-adapter-protocol/implementors/adapters/) in the server and client.
So it is possible now to debug your Pharo application from VSCode

## v0.0.5

### Users

#### LSP

- Bug fix when using printIt and showIt command with the current editor closed (or closed and then open again)

## v0.0.4

### Users

We introduced the [LSP](https://microsoft.github.io/language-server-protocol/).
It is now possible to get helps from a Pharo image inside VScode
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@
"description": "Highlighting, Auto-completion, Execution, ...",
"author": "Benoît Verhaeghe",
"license": "MIT",
"version": "0.0.6",
"version": "0.0.7",
"repository": {
"type": "git",
"url": "https://github.com/badetitou/vscode-pharo"
Expand Down

0 comments on commit 7f581f3

Please sign in to comment.