-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update "Building a connector the hard way" doc #9008
Conversation
8901a38
to
512bd22
Compare
docs/connector-development/tutorials/build-a-connector-the-hard-way.md
Outdated
Show resolved
Hide resolved
@@ -836,7 +836,7 @@ A full connector in less than 200 lines of code. Not bad! We're now ready to pac | |||
|
|||
Our connector is very lightweight, so the Dockerfile needed to run it is very light as well. We edit the autogenerated `Dockerfile` so that its contents are as followed: | |||
|
|||
```text | |||
```Dockerfile |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FWIW if gitbook doesn't show know what Dockerfile
is supposed to do it might format it completely incorrectly. This isn't displayed on gitbook so no issues for now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yay markdown. at the very least vscode and github both display this correctly, so 🤞
also @edgao fwiw if there are portions of the PR template which are irrelevant (e.g: customer impact or checklist in this case) you can delete them to reduce visual clutter |
Co-authored-by: Sherif A. Nada <[email protected]>
What
Update docs for clarity and correctness
How
Recommended reading order
First commit is pure whitespace. Next two commits are the interesting ones.