-
Notifications
You must be signed in to change notification settings - Fork 591
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
[DOC] Bug in Plugins Placements JS-Example #3364
Conversation
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.
Thanks @Sa-Schmi. Pardon the delay. Small PRs are welcome if it improves readability. I see in this case you were aiming for improving consistency. Also welcomed. Note that plugin documentation will probably be improved internally in the coming months. Thanks!
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## develop #3364 +/- ##
===========================================
+ Coverage 15.91% 16.01% +0.10%
===========================================
Files 572 572
Lines 70525 71155 +630
Branches 741 800 +59
===========================================
+ Hits 11222 11397 +175
- Misses 59303 59758 +455
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
What changes are proposed in this pull request?
Fixed a small bug/ copy-paste mistake in the plugin docs.
Do you prefer small PRs like this, or should I write issues for stuff like this instead?
What areas of FiftyOne does this PR affect?
fiftyone
Python library changes