Skip to content

Commit 659c30a

Browse files
committed
blog syntax highlighting improvements
1 parent 30a4e38 commit 659c30a

File tree

3 files changed

+8
-8
lines changed

3 files changed

+8
-8
lines changed

blog/2023-07-05-implement-cadence-worker-from-scratch.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ func main(){
3333

3434
Next, let's define some basic configurations for the worker. In real production environment, you may need to implement them in configurational languages, but in this tutorial, let's just hard code them for now.
3535

36-
```Go
36+
```go
3737
var HostPort = "127.0.0.1:7933"
3838
var Domain = "test-domain"
3939
var TaskListName = "test-worker"
@@ -45,7 +45,7 @@ Note that the domain is what we've already registered in advance. We will need t
4545

4646
Then let's write a simple function to build a Cadence client on gRPC in your worker, which will communicate with the Cadence backend continuously.
4747

48-
```Go
48+
```go
4949
func buildCadenceClient() workflowserviceclient.Interface {
5050
dispatcher := yarpc.NewDispatcher(yarpc.Config{
5151
Name: ClientName,
@@ -70,7 +70,7 @@ func buildCadenceClient() workflowserviceclient.Interface {
7070

7171
Let's also build a logger to help us debug our application
7272

73-
```Go
73+
```go
7474
func buildLogger() *zap.Logger {
7575
config := zap.NewDevelopmentConfig()
7676
config.Level.SetLevel(zapcore.InfoLevel)
@@ -87,7 +87,7 @@ func buildLogger() *zap.Logger {
8787

8888
With both client and logger helper function ready, let's write the function that starts our worker.
8989

90-
```Go
90+
```go
9191
func startWorker(logger *zap.Logger, service workflowserviceclient.Interface) {
9292
// TaskListName identifies set of client workflows, activities, and workers.
9393
// It could be your group or client or application name.

blog/2024-10-01-announcing-cadence-helm-charts-v0.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -22,19 +22,19 @@ Today, we are happy to announce the release of [Cadence Kubernetes Helm Chart v0
2222

2323
Once Helm has been set up correctly, add the repo as follows:
2424

25-
```
25+
```bash
2626
helm repo add cadence https://uber.github.io/cadence-charts
2727
```
2828

2929
If you had already added this repo earlier, run `helm repo update` to retrieve the latest versions of the packages. You can then run `helm search repo cadence` to see the charts.
3030

3131
To install the cadence chart:
32-
```
32+
```bash
3333
helm install my-cadence cadence/cadence
3434
```
3535

3636
To uninstall the chart:
37-
```
37+
```bash
3838
helm delete my-cadence
3939
```
4040

blog/zonal-isolation-v1/zonal-isolation-v1.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -103,7 +103,7 @@ To support Zonal Isolation, please upgrade your SDK versions:
103103
Drains can be done via the [Admin APIs](https://github.com/cadence-workflow/cadence-idl/blob/50a4ee241e50c6baab8e5d47540b176c5ee022a4/proto/cadence-workflow/cadence/admin/v1/service.proto#L125) of cadence-frontend or CLI.
104104

105105
You can check the help message for the CLI by running:
106-
```
106+
```bash
107107
cadence admin isolation-groups -h
108108
```
109109
## Monitoring

0 commit comments

Comments
 (0)