feat: [FC-0070] Manage Tags interoperation - #1454
Conversation
|
Thanks for the pull request, @PKulkoRaccoonGang! This repository is currently maintained by Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are 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. DetailsWhere 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. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #1454 +/- ##
==========================================
+ Coverage 93.33% 93.38% +0.04%
==========================================
Files 1108 1109 +1
Lines 22045 22145 +100
Branches 4674 4692 +18
==========================================
+ Hits 20575 20679 +104
+ Misses 1405 1401 -4
Partials 65 65 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
3e33967 to
487d38f
Compare
8bf4836 to
b87a550
Compare
b87a550 to
62af3bd
Compare
|
Sandbox deployment successful 🚀 |
| if (queryKey[0] === 'taxonomies') { | ||
| return { | ||
| data: { | ||
| results: [], | ||
| }, | ||
| isSuccess: true, | ||
| }; | ||
| } |
There was a problem hiding this comment.
Generally instead of mocking react-query we prefer to mock the API requests using the mocks defined in content-tags-drawer/data/api.mocks.ts.
So you can just write something like this at the top of your test file:
If you do want/need to keep it this way though, you should at least replace the 'taxonomies' string with taxonomyQueryKeys.all from here.
There was a problem hiding this comment.
I like the option with mocks from content-tags-drawer the most, but unfortunately I couldn't run the tests successfully. Probably the problem is related to this mock @tanstack/react-query
Added taxonomyQueryKeys.all instead of the taxonomies line
There was a problem hiding this comment.
Yeah those mocks won't work if you mock out react-query entirely.
There was a problem hiding this comment.
Added taxonomyQueryKeys.all instead of the taxonomies line
Do you mind if we stop here?
There was a problem hiding this comment.
Yeah that's fine. No need to rewrite it, but in the future be aware of the existing mocks we have (as well as everything in testUtils.tsx as they make writing new tests way simpler.
6944a90 to
b112c32
Compare
b112c32 to
27c4533
Compare
|
Sandbox deployment successful 🚀 |
|
Sandbox deployment successful 🚀 |
arbrandes
left a comment
There was a problem hiding this comment.
This works well, and the code looks good. Approved!
|
Oh, and thank a bunch for fixing the scrolling issue! |
* test: Remove support for Node 18 * chore: update code coverage artifact naming
🚨 Dependencies:
Description
Added interaction between MFE and Legacy tagging functionality for xblocks on the Course unit page.
Useful information to include:
Testing instructions
Screen.Recording.2025-02-24.at.15.35.58.mov
Other information
Settings