-
Notifications
You must be signed in to change notification settings - Fork 76
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
Enable capa problem editor for components in libraries [FC-0062] #1290
Enable capa problem editor for components in libraries [FC-0062] #1290
Conversation
Thanks for the pull request, @bradenmacdonald! 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. |
interface AssetResponse { | ||
assets: Record<string, string>[]; // In the raw response here, these are NOT camel-cased yet. | ||
} | ||
|
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.
Most of the functions below are unchanged other than adding types - I just had to move them higher up in the file.
}; | ||
|
||
export default Object.keys(apiMethods).reduce( | ||
(obj, key) => ({ ...obj, [key]: checkMockApi(key) }), |
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 mock API was for the preview server that existed in frontend-lib-content-components
. Last time I tried it, it wasn't working at all, and now that we've moved the code to frontend-app-authoring, it doesn't even exist. So I deleted the unused mockApi code.
|
||
export default { | ||
videoDataProps, | ||
problemDataProps, |
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.
These weren't used anymore (?), but they look like they'll be useful if/when we add more types to these APIs / to the redux state, so I kept the info here, just commented out.
3b6947e
to
4e6f3bd
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #1290 +/- ##
==========================================
+ Coverage 92.38% 92.47% +0.08%
==========================================
Files 1023 1025 +2
Lines 18930 18977 +47
Branches 3967 4036 +69
==========================================
+ Hits 17489 17549 +60
+ Misses 1376 1363 -13
Partials 65 65 ☔ View full report in Codecov by Sentry. |
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.
👍 Working perfectly @bradenmacdonald .
There's some code comments in the tests that need updating, and I have one suggestion around parsing opaque keys, but it shouldn't block merging.
- I tested this using the PR test instructions.
- I read through the code
- I checked for accessibility issues by using my keyboard only to navigate the screens.
- Includes documentation -- code comments mark out TODOs and odd behaviours.
-
User-facing strings are extracted for translationN/A
// Though first we need to fake the request or else the problem type selection UI won't display: | ||
dispatch(actions.requests.completeRequest({ requestKey: RequestKeys.fetchAdvancedSettings, response: {} })); |
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.
😮
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.
@bradenmacdonald Looks good 👍
dfbf0af
to
d7e185b
Compare
Description
Implements #1086
Builds on #1280 and can't merge until after that one is merged.
Private ref: FAL-382
Testing instructions
TODO
Solve the problem that components in search results aren't updated synchronously after changes are saved.done separate in edx-platform PRmaster
before merging.