Skip to content

Commit 4c716f4

Browse files
fixing build error
Signed-off-by: saurabhraghuvanshii <saurabhsraghuvanshi@gmail.com>
1 parent 9ec8cd7 commit 4c716f4

2 files changed

Lines changed: 37 additions & 14 deletions

File tree

gatsby-config.js

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,7 @@ module.exports = {
1515
flags: {
1616
FAST_DEV: true,
1717
PARALLEL_SOURCING: false, // Disable parallel sourcing to reduce memory pressure
18+
DEV_SSR: false,
1819
},
1920
trailingSlash: "never",
2021
plugins: [
@@ -361,6 +362,8 @@ module.exports = {
361362
name: "collections",
362363
},
363364
},
365+
"gatsby-plugin-sharp",
366+
"gatsby-transformer-sharp",
364367
{
365368
resolve: "gatsby-source-filesystem",
366369
options: {

src/collections/blog/2021/2021-04-24-buf-protocols/index.mdx

Lines changed: 34 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: "Adithya Krishna"
66
thumbnail: ./buf-protocol.webp
77
darkthumbnail: ./buf-protocol.webp
88
category: "Cloud Native"
9-
tags:
9+
tags:
1010
- gRPC
1111
published: true
1212
resource: true
@@ -21,21 +21,33 @@ import Problems from "./problems.webp";
2121
<BlogWrapper>
2222
<BufProtocol>
2323

24-
25-
<div className="intro" style="text-align:center;margin: 2rem 4rem;">At Layer5, we are continuously evaluating new technologies and incorporating them into our open source projects. Buf is one of those projects. This post presents an overview of Buf.</div>
26-
24+
<div className="intro" style={{ textAlign: "center", margin: "2rem 4rem" }}>
25+
At Layer5, we are continuously evaluating new technologies and incorporating
26+
them into our open source projects. Buf is one of those projects. This post
27+
presents an overview of Buf.
28+
</div>
2729

2830
## What is Buf?
2931

3032
A tool to make Protobuf reliable and easy to use for service owners and clients, while keeping it the obvious choice on the technical merits.
3133
Our organization should not have to reinvent the wheel to create, maintain, and consume Protobuf APIs efficiently and effectively. It will handle our Protobuf management strategy for us, so we can focus on what matters.
32-
<div className="fact">Learn more about Buf Protocol, visit <a href="https://buf.build" rel="nofollow">Buf Protocol</a> or their documentation at <a href="https://docs.buf.build/" rel="nofollow">Buf Protocol Docs</a></div>
34+
35+
<div className="fact">
36+
Learn more about Buf Protocol, visit{" "}
37+
<a href="https://buf.build" rel="nofollow">
38+
Buf Protocol
39+
</a>{" "}
40+
or their documentation at{" "}
41+
<a href="https://docs.buf.build/" rel="nofollow">
42+
Buf Protocol Docs
43+
</a>
44+
</div>
3345

3446
<img className="problem-image" src={Problems} />
3547

36-
## Features
48+
## Features
3749

38-
- Automatic file discovery.
50+
- Automatic file discovery.
3951
- Selectable configuration - 40 lint checkers and 54 breaking checkers
4052
- Selectable error output - `file:line:col:message`
4153
- Check anything from anywhere - proto files, tar, git, pre-built images or file descriptors.
@@ -52,31 +64,39 @@ Buf attempts to simplify your Protocol Buffers workflow using the Buf CLI and pr
5264
- A configurable file builder that produces Images, our extension of FileDescriptorSets.
5365

5466
## Comparison Between Protobuf and Buf
67+
5568
Layer5 projects currently use protoc as the tool for building their protobuf defintions. The following are some considerations made while determining whether to use Buf.
5669

5770
- Protobuf is not as widely adopted as JSON.
58-
- API Structure
71+
- API Structure
5972
- No standards enforcement
60-
- Inconsistency can arise across an organization's Protobuf APIs,
73+
- Inconsistency can arise across an organization's Protobuf APIs,
6174
- Design decisions can be made that can affect your API's future iterability.
6275
- Backward Compatibility
6376
- Stub distribution
6477
- Tooling
6578

6679
Buf aims to solve the above problems and it's long-term goal is to enable schema-driven development: A future where APIs are defined consistently, in a way that service owners and us can depend on
80+
6781
## Roadmap to Adopting Buf
82+
6883
In consideration of the use of Buf, we would adopt it in phases, starting with the following ares of integration.
6984

70-
- **API Structure Enforcements**
71-
- Linter solves this issue by enforcing standards.
72-
- Also, we don’t need to use Buf as a standalone tool we can just use linter as plugins.
85+
- **API Structure Enforcements**
7386

87+
- Linter solves this issue by enforcing standards.
88+
- Also, we don’t need to use Buf as a standalone tool we can just use linter as plugins.
7489

7590
- **Backward Compatibility**
7691
- It will check for different things that can cause breaking change.
7792
- For example, type change.
7893

79-
<div className="intro">If these topics excite you and you want to explore more <a href="/resources">cloud native technolgies</a>, come and say "Hi" on the community <a href="http://slack.layer5.io">Slack</a> and you are sure to be warmly welcomed. <span>😀</span></div>
94+
<div className="intro">
95+
If these topics excite you and you want to explore more{" "}
96+
<a href="/resources">cloud native technolgies</a>, come and say "Hi" on the
97+
community <a href="http://slack.layer5.io">Slack</a> and you are sure to be
98+
warmly welcomed. <span>😀</span>
99+
</div>
80100

81101
</BufProtocol>
82-
</BlogWrapper>
102+
</BlogWrapper>

0 commit comments

Comments
 (0)