update the svr searcher documentation and add code snippets in ts/go #2542
+402
−31
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
KMontag42
requested review from
gfletcher-cll,
aelmanaa and
khadni
as code owners
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
KMontag42
commented
Apr 11, 2025
gfletcher-cll
approved these changes
Apr 11, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closing issues
closes #DOC-994
Description
Updates the SVR Searcher documentation with several code snippets, extra considerations, and more detailed steps to help onboard searchers more rapidly.
Changes
1. High Level StepsconsiderationsTagscomponent so that we can do the tabbed code language selection on the documentation code samplesNOTE
It would be great if we could make the
samples/DataFeeds/SVR/decoding-abi.jsonfile a single line file, but the prettier git hook wouldn't let me.Not the biggest deal if we cannot do that, but it would save some vertical space :)