-
Notifications
You must be signed in to change notification settings - Fork 19.6k
Fix typos in string_lookup #20667
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
base: master
Are you sure you want to change the base?
Fix typos in string_lookup #20667
Conversation
I observed a few typos in string_lookup
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #20667 +/- ##
=======================================
Coverage 81.95% 81.95%
=======================================
Files 543 543
Lines 50663 50663
Branches 7828 7828
=======================================
Hits 41523 41523
Misses 7246 7246
Partials 1894 1894
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
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.
Please fix the code formatting.
indices. Defaults to `"[UNK]"`. | ||
vocabulary: Optional. Either an array of integers or a string path to a | ||
text file. If passing an array, can pass a tuple, list, | ||
1D NumPy array, or 1D tensor containing the integer vocbulary terms. | ||
text file. If passing an array,you can pass a tuple, list, |
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.
Please add a space after the comma and before "you".
This PR is stale because it has been open for 14 days with no activity. It will be closed if no further activity occurs. Thank you. |
I observed a few typos in string_lookup