instruction correction to no-longer-existing Scorers tab DOCS-1912#2196
Open
anastasiaguspan wants to merge 2 commits intomainfrom
Open
instruction correction to no-longer-existing Scorers tab DOCS-1912#2196anastasiaguspan wants to merge 2 commits intomainfrom
anastasiaguspan wants to merge 2 commits intomainfrom
Conversation
Contributor
🔗 Link Checker Results✅ All links are valid! No broken links were detected. Checked against: https://wb-21fd5541-fix-annotation-scorer-docs-1912.mintlify.app |
dbrian57
approved these changes
Feb 26, 2026
Contributor
dbrian57
left a comment
dbrian57
left a comment
There was a problem hiding this comment.
Minor suggestions inline. Looks good, though!
| ## Provide feedback through the SDK | ||
|
|
||
| > You can find SDK usage examples for feedback in the UI under the **Use** tab in the call details page. | ||
| > You can find SDK usage examples for feedback in the UI under the **Use** tab in the Call details panel. |
Contributor
There was a problem hiding this comment.
Suggested change
| > You can find SDK usage examples for feedback in the UI under the **Use** tab in the Call details panel. | |
| You can find SDK usage examples for feedback in the UI under the **Use** tab in the Call details panel. |
pretty sure we don't need to indent this.
| > You can find SDK usage examples for feedback in the UI under the **Use** tab in the call details page. | ||
| > You can find SDK usage examples for feedback in the UI under the **Use** tab in the Call details panel. | ||
|
|
||
| You can use the Weave SDK to programmatically add, remove, and query feedback on calls. |
Contributor
There was a problem hiding this comment.
Suggested change
| You can use the Weave SDK to programmatically add, remove, and query feedback on calls. | |
| You can use the Weave Python SDK to programmatically [add](/weave/reference/python-sdk/trace/feedback#method-add), [remove](/weave/reference/python-sdk/trace/feedback#method-purge), and [query feedback](/weave/reference/python-sdk/trace/weave_client#method-get_feedback) on calls. The TypeScript SDK does not currently support feedback functionality. |
I know this was outside the scope of this PR, but this definitely needed some links 😅
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
The main fix requested here was to fix blatantly bad instructions (there is no Scores in the project sidebar anymore). This primary change is a procedure at line 250/247
Whilst there, i did a pass through the page for cleanup and naming standarization.
Note: although the screenshots are still 'mostly' correct, they do show the out of date project sidebar and should be updated. I didn't update them at this time though because this human annotation is a different/old way to do the new annotation queue/annotation field stuff - so i'm not sure if this content has any life left once annotation queues goes GA. also, they need to rename some stuff to consistency (they're called 'scorers' here when they're called 'fields' in the new stuff, i let them know they should make these consistent). we can take new screenshots when all that gets sorted out.
(plus a random fix on another page for "Call details panel" instead of calling it a page (on the Traces page).
Testing
mint dev)mint broken-links)