openwhisk-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rab...@apache.org
Subject [openwhisk-runtime-go] branch master updated: Fixed typo in link to VSCode and added syntax highlighter to golang code (#112)
Date Sat, 09 Nov 2019 15:55:41 GMT
This is an automated email from the ASF dual-hosted git repository.

rabbah pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/openwhisk-runtime-go.git


The following commit(s) were added to refs/heads/master by this push:
     new 1638a72  Fixed typo in link to VSCode and added syntax highlighter to golang code
(#112)
1638a72 is described below

commit 1638a72c1a8cdee5d14e1fe4b755cc0fefc55128
Author: agilob <agilob@users.noreply.github.com>
AuthorDate: Sat Nov 9 15:55:35 2019 +0000

    Fixed typo in link to VSCode and added syntax highlighter to golang code (#112)
---
 docs/DEPLOY.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/DEPLOY.md b/docs/DEPLOY.md
index 55f6e11..9d9b696 100644
--- a/docs/DEPLOY.md
+++ b/docs/DEPLOY.md
@@ -92,7 +92,7 @@ If you want for example use the library `github.com/sirupsen/logrus` to
manage y
 
 For example consider you have in the file `src/hello/hello.go` the import:
 
-```
+```go
 import "github.com/sirupsen/logrus"
 ```
 
@@ -129,7 +129,7 @@ If you need to use vendor folder in the main package, you need to create
a direc
 
 ### Using VsCode
 
-If you are using [VsCode[(https://code.visualstudio.com/) as your Go development environment
with the [VsCode Go](https://marketplace.visualstudio.com/items?itemName=ms-vscode.Go) support,
and you want to get rid of errors and have it working properly, you need to configure it to
support the suggested:
+If you are using [VsCode](https://code.visualstudio.com/) as your Go development environment
with the [VsCode Go](https://marketplace.visualstudio.com/items?itemName=ms-vscode.Go) support,
and you want to get rid of errors and have it working properly, you need to configure it to
support the suggested:
 
 - you need to have a `src` folder in your source
 - you need either to open the `src` folder as the top level source or add it as a folder
in the workspace (not just have it as a subfolder)


Mime
View raw message