Napari join labels

[maliagehan]

Describe your changes
A clear and concise description of what changes are made by this pull request.
What was the previous functionality (if relevant) and what can we do now with
these changes.

Type of update
Is this a:

• New feature or feature enhancement
• Update to documentation

Associated issues
Reference associated issue numbers. Does this pull request close any issues? #12

Additional context
Add any other context about the problem here.

For the reviewer
See this page for instructions on how to review the pull request.

• PR functionality reviewed in a Jupyter Notebook
• All tests pass
• Test coverage remains 100%
• Documentation tested
• New documentation pages added to plantcv/mkdocs.yml
• Changes to function input/output signatures added to updating.md
• Code reviewed
• PR approved

[deepsource-io]

Here's the code health analysis summary for commits 9fe576f..73ce255. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
Python	✅ Success		View Check ↗
Test coverage	✅ Success		View Check ↗

Code Coverage Report

Metric	Aggregate	Python
Branch Coverage	100%	100%
Composite Coverage	100%	100%
Line Coverage	100%	100%
New Branch Coverage	100%	100%
New Composite Coverage	100%	100%
New Line Coverage	100%	100%

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[maliagehan]

notebooks to test are available on workspace jupyter>pcv-annotate-prs>pr13-napari-join-labels. Sorry there are multiple functions. There is a notebook for each function for testing.

[maliagehan]

Realized by adding the printing option that I should save that out to a temp file in the test, will update that

[k034b363]

Plantcv-annotate doesn't yet have an updating.md, so these changes would need to be added to that if it is created later. Notebook used for testing functionality stored in data_science/jupyter/pcv-annotate-prs/pr13-napari-join-labels/review_materials_KB/

[HaleySchuhl]

I believe the changelog.md is serving the same purpose as updating.md in the add-on repositories, so we can add new functions there. And then once it's packaged up on Conda and/or pip then we might want to add a doc page for versioning.

[nfahlgren]

I changed the name to changelog for the add-on packages because that's really what we use the updating page for. I don't think we need a separate page for versioning as we don't really use the existing page for that per se.