-
Notifications
You must be signed in to change notification settings - Fork 26
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
misc: Docs Update + Other non-functional changes #87
Conversation
Codecov Report
@@ Coverage Diff @@
## master #87 +/- ##
==========================================
+ Coverage 67.66% 69.25% +1.59%
==========================================
Files 32 36 +4
Lines 1976 2417 +441
==========================================
+ Hits 1337 1674 +337
- Misses 570 651 +81
- Partials 69 92 +23
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
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.
Looks like good changes to me!
@@ -0,0 +1,7 @@ | |||
default: true |
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.
I personally use VSCode so I am fine with this change but wondering what others think about adding IDE/editor/extension specific config files in the root dir.
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.
What do you think about adding exportloopref
?
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.
I only looked at the README but it looks like a good addition to me and the benefits seem to outweigh the possibilities of false negatives
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.
see cbe1692
FYI - it didn't actually catch the problem. But we're also using it in go-algorand
so it should be safe.
I pulled out the doc updates from draft PR #83 and also fixed a couple of scoping issues in our tests.
Summary of Changes
.markdownlint.yml
. This isn't enforced in CI but while using the VS Code extension it helped me identify some bugs in our docs. For example, some improperly formatted list items.docs/Configuration.md
docs/Development.md
docs/GettingStarted.md
docs/tutorials/WritingBlocksToFile.md
conduit/pipeline/pipeline_test.go
conduit/plugins/importers/algod/algod_importer_test.go
(also tightening the test expectations around the genesis object received fromInit()
)TODO
exportloopref
to our linters?