Conversation
|
Thanks for the pull request, @pomegranited! What's next?Please work through the following steps to get your changes ready for engineering review: 🔘 Get product approvalIf you haven't already, check this list to see if your contribution needs to go through the product review process.
🔘 Provide contextTo 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:
🔘 Get a green buildIf 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 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:
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:
💡 As a result it may take up to several weeks or months to complete a review and merge your PR. |
2a5bfac to
f4a6350
Compare
which uniquely identifies a Collection within a Learning Package. Existing Collection keys are initialized with a random string.
to identify Collections. We do this because the `key` will be used in the Collection's opaque key (not the ID).
a300346 to
56b5fb6
Compare
rpenido
left a comment
There was a problem hiding this comment.
Hi @pomegranited! This is looking good!
Only a few nits
| User-facing string representation of a Collection. | ||
| """ | ||
| return f"<{self.__class__.__name__}> ({self.id}:{self.title})" | ||
| return f"<{self.__class__.__name__}> ({self.key}:{self.title})" |
There was a problem hiding this comment.
This would not be unique. Do you think we should add the library key here?
openedx_learning/apps/authoring/collections/migrations/0004_collection_key.py
Outdated
Show resolved
Hide resolved
| key: str, | ||
| *, | ||
| title: str | None = None, | ||
| description: str | None = None, |
There was a problem hiding this comment.
Sorry for not catching this before. 😞
I think we should be able to update the key here.
| description: str | None = None, | |
| description: str | None = None, | |
| new_key: str, |
There was a problem hiding this comment.
Hmm.. if we allow that, it'll change the Collection's opaque key, which will disconnect it from any applied tags.. so I think it should be immutable.
rpenido
left a comment
There was a problem hiding this comment.
LGTM 👍
Thank you for your work, @pomegranited!
I commented about adding a new parameter to allow the user to update the key. Other than that, everything is good on my end.
- I tested this using the instructions from openedx/openedx-platform#35321
- I read through the code
-
I checked for accessibility issues - Includes documentation
|
Hi @ormsbee , this is a minor PR, but I'd appreciate your review if you have time? |
rpenido
left a comment
There was a problem hiding this comment.
Thank you for the changes, @pomegranited!
LGTM 👍
Description
Adds a new required field to the Collection model:
key(string), which uniquely identifies a Collection within a Learning Package.Existing Collection keys are initialized with a random string.
Supporting information
Part of : openedx/modular-learning#226
Private-ref: FAL-3783
Testing instructions
See openedx/openedx-platform#35321 for full testing instructions.
Testing migrations:
In an openedx-learning virtual environment, run:
main, and runpython3 manage.py migratepython3 manage.py shell:open-craft/jill/collection-keypython3 manage.py migratepython3 manage.py shell: