-
Notifications
You must be signed in to change notification settings - Fork 21
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
feat: adds events to handle changes in xblocks #143
feat: adds events to handle changes in xblocks #143
Conversation
Thanks for the pull request, @navinkarkera! Please note that it may take us up to several weeks or months to complete a review and merge your PR. Feel free to add as much of the following information to the ticket as you can:
All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here. Please let us know once your PR is ready for our review and all tests are green. |
Hello! Thanks for your contribution! I'll review this as soon as I can. |
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.
@navinkarkera Nice work covering all the necessary parts including the avro tests. I have noted one question about the data classes introduced here and some minor typos. Can you kindly address those?
@navinkarkera One thing that kind of stood out from the PR description was this question:
The answer is specific to skill tagging which is great. It can also be more generally answered, as the event is only passing the This is just a note, to help myself understand the scope of the change here and aid other reviewers, if needed. No action item here :) |
0d1598d
to
87822e2
Compare
@tecoholic Thanks for the suggestions! Updated the MR.
Makes absolute sense. Thanks, i'll add this to the description. |
@mariajgrimaldi Sorry, when I clicked on request-a-review-again button for @tecoholic, it removed you from reviewers list and I cannot add you back.
Thank you! |
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.
- I tested this: As this only introduces the data classes and the signals, there wasn't anything specific to test. The unit tests are passing, that validates the data classes.
- I read through the code
- I checked for accessibility issues - NA
- Includes documentation - It contains inline documentation as expected.
7d15816
to
7fbda3e
Compare
do you have a working example for testing? if so, can you add instructions to the PR description? thanks! |
7fbda3e
to
9578c40
Compare
@mariajgrimaldi I don't have one yet as the work on the edx-platform side is pending. I do want to add one more signal and data class to send list of verified skill ids and xblock usage_key. The idea is that users will verify the tags/skills associated to an XBlock. We want to send this data via openedx-event signals to course-discovery and update the relevant tables. I was wondering whether I should add it in the same MR or create a separate MR once this is merged. Do let me know your thoughts here. |
@navinkarkera: it's best to create a separate PR for those changes. @felipemontoya: what do you think of these changes? I'd like to test a working version, for now, this looks quite good! |
9578c40
to
32d9664
Compare
@mariajgrimaldi Thanks! I have created a separate MR: open-craft#1 on top of this branch. The new event requires support for array types so it is also added in the MR. Please have a look. |
32d9664
to
df0fc92
Compare
@mariajgrimaldi Any updates on this? Let me know if something needs to be changed. |
@mariajgrimaldi Gentle reminder. |
@navinkarkera: I'm out until Dec 20, I'll check on this when I'm back. Sorry for the delay. Unless @felipemontoya can pick this up. I dismissed my review so it's not a blocker. |
I'm out of office and can't continue the review
can you rebase with main? thank you! |
@mariajgrimaldi It is already up to date. |
I thought rebasing would help with the coverage issue. Can you check that so we can merge? Let me know if you need help! |
@mariajgrimaldi Running Not sure how to proceed here. Should we implement tests for missing lines even if they are not related to any change in this MR? Please advice. |
@mariajgrimaldi Friendly ping on @navinkarkera's comment above. |
I'm back on monday. I'll take a look at this then. Sorry for the delay! |
hello! can you rebase with main? The codecov for the project changed, so I think it'll pass this time |
1934a83
to
6d86019
Compare
@mariajgrimaldi Updated! Please approve the workflow. |
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.
This looks great! Just one last thing, can you update the changelog entry date? thanks!
fix: documentation typo fix: remove unwanted comments and rename XBlockData docs: docstrings in tests for usage key serialization refactor: rename XBlockDuplicatedData to DuplicatedXBlockData chore: bump version and update changelog chore: bump version and update changelog fix: import order chore: bump version docs: generalize signal docs docs: update xblock_published signal docs
6d86019
to
faad90a
Compare
@mariajgrimaldi Thanks! Updated. |
@navinkarkera 🎉 Your pull request was merged! Please take a moment to answer a two question survey so we can improve your experience in the future. |
This commit combines changes implemented in following commits: - cc1889b - ec2a581 The changes were reverted as part of commit a999401 as the upstream MR in openedx-events: openedx/openedx-events#143 was not merged. It is now merged and the dependencies are udpated.
This commit combines changes implemented in following commits: - cc1889b - ec2a581 The changes were reverted as part of commit a999401 as the upstream MR in openedx-events: openedx/openedx-events#143 was not merged. It is now merged and the dependencies are udpated.
This commit combines changes implemented in following commits: - cc1889b - ec2a581 The changes were reverted as part of commit a999401 as the upstream MR in openedx-events: openedx/openedx-events#143 was not merged. It is now merged and the dependencies are udpated.
This commit combines changes implemented in following commits: - cc1889b - ec2a581 The changes were reverted as part of commit a999401 as the upstream MR in openedx-events: openedx/openedx-events#143 was not merged. It is now merged and the dependencies are udpated.
This commit combines changes implemented in following commits: - cc1889b - ec2a581 The changes were reverted as part of commit a999401 as the upstream MR in openedx-events: openedx/openedx-events#143 was not merged. It is now merged and the dependencies are udpated.
…enedx#138) This commit combines changes implemented in following commits: - cc1889b - ec2a581 The changes were reverted as part of commit a999401 as the upstream MR in openedx-events: openedx/openedx-events#143 was not merged. It is now merged and the dependencies are udpated.
Description: Adds events and data classes to allow consumers to react on xblock events like published, deleted and duplicated.
The idea is to fire these events in delete_item, publish_item and _duplicate_item and update skills related to the xblock in taxonomy-connector (part of course-discovery).
Answer for a question asked in previous similar MRs:
Do consumers have to make separate requests to get more information?
Generally: Additional data if required related to the event needs to be fetch separately as it can be different for different use case.
Specifically for skill tagging: Yes, for skill tagging to work we need concatenated text representation of children xblocks for units and transcript for video xblocks which can be extracted using index_dictionary of the xblock. The idea is to add a new api to fetch block metadata and use this API in taxonomy-connector.
Related MRs:
These MRs are the foundation for storing skills related on xblocks level, specifically for unit and video xblocks.
ISSUE: Link to GitHub issue
Merge checklist:
Post merge:
finished.
Author concerns: List any concerns about this PR - inelegant
solutions, hacks, quick-and-dirty implementations, concerns about
migrations, etc.