feat: add existing content to a collection [FC-0062]

[rpenido]

Description

This PR implements a feature that allows library components to be added to a collection using the add-content sidebar.

More information

• Part of:
  • Collections Page - Add existing content from within a collection #1173

Testing instruction

1. Open the Library Authoring page
2. Open a collection
3. Click on the "New" button
4. Click on the "Existing Library Content"
5. Select some components and then click on the "Add to collection" button

---

Private ref: FAL-3901}

[openedx-webhooks]

Thanks for the pull request, @rpenido!

What's next?

Please work through the following steps to get your changes ready for engineering review:

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

🔘 Let us know that your PR is ready for review:

Who will review my changes?

This repository is currently maintained by @openedx/2u-tnl. Tag them in a comment and let them know that your changes are ready for review.

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

[codecov]

Codecov Report

Attention: Patch coverage is 98.03922% with 1 line in your changes missing coverage. Please review.

Project coverage is 93.15%. Comparing base (11470f2) to head (806f32f).
Report is 3 commits behind head on master.

Files with missing lines	Patch %	Lines
...rary-authoring/add-content/AddContentContainer.tsx	88.88%	1 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #1416   +/-   ##
=======================================
  Coverage   93.15%   93.15%           
=======================================
  Files        1051     1053    +2     
  Lines       20328    20373   +45     
  Branches     4335     4342    +7     
=======================================
+ Hits        18936    18979   +43     
+ Misses       1332     1331    -1     
- Partials       60       63    +3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[pomegranited]

👍 Works beautifully @rpenido !

I'll see if I can help with the circular imports.

• I tested this on my dev stack using the PR test instructions
• I read through the code and tests
• I checked for accessibility issues by using my keyboard to navigate
• Includes documentation -- code comments
• User-facing strings are extracted for translation

[kdmccormick]

@rpenido Feel free to ping me if you are looking for a reviewer/merger on this one

[rpenido]

@rpenido Feel free to ping me if you are looking for a reviewer/merger on this one

That would be awesome @kdmccormick!
This is ready for review. I'm just waiting for the CD/CI to check if everything is fine.

[kdmccormick]

Suggested change

	/** The component picker modal to use. We need to pass it as a reference instead of
	* directly importing it to avoid the import cycle:
	* ComponentPickerModal > ComponentPicker > LibraryAuthoringPage/LibraryCollectionPage >
	* Sidebar > AddContentContainer > ComponentPickerModal */
	{/** The component picker modal to use. We need to pass it as a reference instead of
	* directly importing it to avoid the import cycle:=
	* ComponentPickerModal > ComponentPicker > LibraryAuthoringPage/LibraryCollectionPage >
	* Sidebar > AddContentContainer > ComponentPickerModal */}

My jsx is rusty, but doesn't this need to be in curly braces?

[bradenmacdonald]

Apparently it's not necessary.

[kdmccormick]

Tested, works great!

[kdmccormick]

Not sure how I feel about using the term "linking" here, since it's very different than linking content to a course. No action needed now, just a potential place for refinement post-Sumac.

[bradenmacdonald]

+1